Timeline for Vote: Do we want code highlighting?
Current License: CC BY-SA 3.0
23 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 20, 2017 at 10:32 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
Mar 17, 2017 at 10:13 | history | edited | CommunityBot |
replaced http://meta.serverfault.com/ with https://meta.serverfault.com/
|
|
Apr 23, 2014 at 13:35 | history | edited | CommunityBot |
Fixup of bad MSO links to MSE links migration
|
|
Apr 23, 2014 at 9:11 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
Feb 6, 2012 at 19:40 | vote | accept | Bart De Vos | ||
Feb 6, 2012 at 18:41 | history | edited | Kevin Montrose |
edited tags
|
|
Jan 26, 2012 at 2:26 | history | tweeted | twitter.com/#!/ServerFault/status/162360781105659904 | ||
Jan 24, 2012 at 11:50 | history | edited | Bart De Vos | CC BY-SA 3.0 |
added 89 characters in body; edited tags
|
Jan 23, 2012 at 19:53 | comment | added | voretaq7 | @ShaneMadden Most of this would of course be moot if people INDENTED THEIR {CODE, CONFIG FILES} :-) | |
Jan 23, 2012 at 19:49 | comment | added | Shane Madden | @voretaq7 Indeed - and non-insane coloring for some of the common config file types we see would be a nice wishlist item. | |
Jan 23, 2012 at 19:42 | comment | added | voretaq7 | @ShaneMadden also acceptable. I'd like stuff like shell scripts to get auto-highlighted, but if it's a choice between "On by default and has to be turned off" or "off by default and has to be turned on" I'd prefer off by default. | |
Jan 23, 2012 at 19:40 | comment | added | Shane Madden | @voretaq7 Or if it's off by default and needs to be manually turned on with the html comment? | |
Jan 23, 2012 at 16:52 | comment | added | voretaq7 | @Zoredache disgusting, but acceptable. I have no objection to syntax highlighting as long as we can make it stop if it's screwing up :) | |
Jan 23, 2012 at 16:41 | comment | added | Zoredache |
@voretaq7, see stackoverflow.com/editing-help#syntax-highlighting. The answer seems to be <!-- language: lang-none --> .
|
|
Jan 23, 2012 at 15:58 | comment | added | voretaq7 |
@MarkHenderson (or anyone else who has used the highlighting features on other sites) -- Is there an equivalent <!-- stop highlighting my file you're doing it wrong! --> tag?
|
|
Jan 23, 2012 at 14:16 | comment | added | Chris S | @MarkHenderson Totally agree, I'm only voting yes to get that option, do not want automatic anything. =] | |
Jan 23, 2012 at 7:55 | comment | added | Bart De Vos | Vote Yes. We will get to the tags-thing later ;). Almost all languages are in the prettifier. Powershell = C#, rest of them are there. | |
Jan 23, 2012 at 7:52 | comment | added | Mark Henderson Mod | btw, if I want code highlighting, but only if it's explicit turned on (with the <!-- --> syntax), should I add a 3rd option, or vote for "yes"? | |
Jan 23, 2012 at 7:51 | history | edited | Mark HendersonMod | CC BY-SA 3.0 |
edited title
|
Jan 23, 2012 at 7:50 | comment | added | Mark Henderson Mod | Does the prettifier support the languages we would expect to see here? Such as powershell/bash/cmd/vbscript? | |
Jan 23, 2012 at 7:22 | answer | added | Bart De Vos | timeline score: 3 | |
Jan 23, 2012 at 7:22 | answer | added | Bart De Vos | timeline score: 25 | |
Jan 23, 2012 at 7:22 | history | asked | Bart De Vos | CC BY-SA 3.0 |