It continues to be an irritant.
Paging @codinghorror or @JoeKGBX: Is there a way a user can add something to a CODE tag to turn off syntax colouring? I’ve been forced to use CODE blocks as the only way to structure tables within posts. Unfortunately, Discourse then colours this as though it were actual code, which is messy.
Sometimes it also goes bonkers for sites like this with a dark background colour:
+1 -2 +3 -4 +5 -6 +7 -8 +9 -10
That’s a series of positive and negative integers, in case you were wondering!
(Also pinging @nathanielmattock in case he’s seen anything about this elsewhere)
Edit: with four space indenting inside the CODE block:
+1 -2 +3 -4 +5 -6 +7 -8 +9 -10
Thanks! Bookmarked for future reference.
Hate to be a pain, but this isn’t working consistently. Please see this post for multiple examples. Throughout, I have used
[code] ... [/code] blocks for all the tables. Some of these are rendered in the expected fixed width font, and some are not. Some have code colouring, and others do not. Inserting four spaces at the start of each line within a
[code] ... [/code] block doesn’t seem to make any difference to the way the block is rendered. (This is all in Firefox 48.0.2 Mac)
Any idea what’s going on here and how to get consistent rendering?
Alternatively, is there any plan to support even very basic wiki-style table mark-up? I really don’t want to resort to replacing every table with a screen shot of an Excel spread sheet…
Usually because people don’t put linebreaks before and after. Don’t butt
text right up against the command.
That’s not what’s happening in this case. Here’s some screen shots I just took so as to focus on the most obvious problem:
What you see in the text editor:
What you see in the actual post:
You’ll notice that the font appears to change part way through the value 0.0483 in the first table row (and yes, I did check that it’s a zero and not a capital o!)
I even tried inserting extra line breaks before and after the code block tags and within the code block tags, but nothing changed at all.
Any other ideas?
You might try using triple backticks instead, or 4 space indent.
If you mean like this:
It doesn’t work - still looks exactly the same. As a little extra back-story, it was actually fine (properly spaced and uniformly in fixed-width serif font) back when I created the post in December 2015. This makes me think that something either in the CSS or in the text processing engine that changed between then and now is choking on this post for some reason.
Item Weight Threshold Probability Relic (Oz kit) 10 0.0483 4.83% Class mod 22 0.1546 10.63% Grenade mod 30 0.2995 14.49% Shield 45 0.5169 21.74% Weapon 100 1.0000 48.31%
Looks like you want 4 space indent, because otherwise it is treating that as actual, literal computer source code – rather than what it is, which is preformatted text. This is screwing up the display.
So indent by 4 spacees. (The toolbar button should do this for you, if you prefer.) Don’t use code semantics unless it’s actual literal source code like “I’m gonna check this into GitHub and then compile it into an executable, yo” source code.
@VaultHunter101 and if you do, dont tell us
Oh Jesus have I posted in the wrong thread… Ok fixed.
Something I’ve been meaning to comment on - after I post sometimes on mobile, it immediately jumps up the page to a much earlier post. This is quite irritating, and it happens regularly for me… I wonder if there’s any way of stopping it?
Well the What made you happy today thread just passed 6000 so that might get locked soon.
Far too much happiness on this forum.
We need to be able to hide the Beta forum for Battleborn.
After a full year and several game-changing updates, I agree. Any value in the open beta discussions regarding characters and gear has long since disappeared.
Yea. Even if they have to hide, archive or move it to a subforum area for everyone.
So, I just tried writing a censored word to describe a certain enemy. Then I did it again in another sentence that was within brackets and noticed that at least for the preview it did not get censored. Sorry for using a mild censored word in my demo below, I’m just not sure if my wording for this is understandable.
this will get cencored: ■■■■■■
(but this will not: asshat)