Skip to main content
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting""There's a bug in the syntax highlighting".

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting".

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting".

Migration of MSO links to MSE links
Source Link

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting""There's a bug in the syntax highlighting".

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting".

There are a few discussions on features of syntax highlighting on Stack Exchange if you look at the related questions area to the right of the question/answer here. The commonly directed one that is most commonly thrown up is "There's a bug in the syntax highlighting".

Nit-picking
Source Link
Crowie
  • 337
  • 1
  • 14

"There's no accounting for taste"

Up to you if you like the colour. I don't mind it but I'm starting to prefer plain text code. I'd prefer something better, something specifically for a trace, and anyway black and white isn't so bad to read anyway. But those two options - nothing or something - are what you're going to get for now on SE.

Personally I think it helps to put colour onto the class names and separate out the packages. To me and others it is going to be marginal but I think the benefits are along the lines of what you get when a question is edited for grammar. It can help more quickly identify the class, package or module that a problem is based within. IfIt's something Eclipse and IntelliJ have seen fit to add. IMO if that makes the question and answer more useful, that's probably going to be a good thing. However, as I said, it's up to your taste but all you get is something or nothing.

"There's no accounting for taste"

Up to you if you like the colour. I don't mind it. I'd prefer something better, something specifically for a trace, and anyway black and white isn't so bad to read anyway. But those two options - nothing or something - are what you're going to get for now on SE.

Personally I think it helps to put colour onto the class names and separate out the packages. To me and others it is going to be marginal but I think the benefits are along the lines of what you get when a question is edited for grammar. It can help more quickly identify the class, package or module that a problem is based within. If that makes the question and answer more useful, that's probably going to be a good thing.

"There's no accounting for taste"

Up to you if you like the colour. I don't mind it but I'm starting to prefer plain text code. I'd prefer something better, something specifically for a trace. But those two options - nothing or something - are what you're going to get for now on SE.

Personally I think it helps to put colour onto the class names and separate out the packages. To me and others it is going to be marginal but I think the benefits are along the lines of what you get when a question is edited for grammar. It can help more quickly identify the class, package or module that a problem is based within. It's something Eclipse and IntelliJ have seen fit to add. IMO if that makes the question and answer more useful, that's probably going to be a good thing. However, as I said, it's up to your taste but all you get is something or nothing.

added 34 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Since the question is a possible duplicate trying to update the last part to reflect that. This should present that stack traces aren't a feature of Prettify and that users wanting that information should go to Prettify which is something that was part of my original answer
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
added 56 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Editing 'hear' the word related to the sense of hearing, to here, the word related to location
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
deleted 1 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
More restructuring and editing; Post Made Community Wiki
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
More restructuring and editing
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Removing the edit tag and resultingly re-arranging the answer to make it more useful
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Seeing if I can improve the answer
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Seeing if I can improve the answer
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Editing based on comment
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
added 15 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Showing what can be done for a Java stacktrace
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
added 29 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
added 48 characters in body
Source Link
Crowie
  • 337
  • 1
  • 14
Loading
Source Link
Crowie
  • 337
  • 1
  • 14
Loading