7

Code formatting for things that are not code is incorrect use of formatting and I edit posts to remove it regularly. Code formatting is never a form of emphasis. Using code formatting for things that are not code… makes the text very hard to read ("My eyes hate you now, well done —Tim Stone") means that web readers for the visually impaired read it l-e-t-t-...


2

The StackExchange developers view and voted up view is if the new question is better then close the old one as the duplicate from this MetaStackExchange question (and that makes sense to me) Note this is not exactly your question but the other questions that match yours are closed as dups of this :( In this case the new question and answer rather obviously ...


2

If there is a built in or predefined option, use it. Simple as that. If a flag is ultimately handled differently to what you want or were expecting, then rest assured it won't be down to the method you used to flag.


1

I think using back ticks for every thing makes things less readable they are for code. (There are several meta.stackoverflow/exchange threads. e.g. this) In your list OS names are definitely not code so Lion Mavericks are OK, similarly application names are plain text. I prefer menu entries as text. The only ones I might use back ticks for are a directory ...


1

I don't really pay attention to who flagged an answer but I am, more and more, declining to remove bad or wrong answers that are flagged because that's not what flagging is supposed to be used for. There's even a canned response to flags that says "Flags should not be used to flag answers with technical inaccuracies or that are altogether incorrect". You ...


Only top voted, non community-wiki answers of a minimum length are eligible