« first day (1751 days earlier)      last day (3209 days later) » 

terdon
terdon
1:01 PM
I think they have all been fixed now but, as a general rule, 1) backticks are only for things you would enter in the command line and 2) should improve readability. There's no reason to have things like OS names in backticks and even some commands don't always need them. They are useful to highlight that a particular string is a command; if you use the command's name 10 times in an answer, having it always in backticks makes it harder, not easier to read.
There's a good thread on meta.AU explaining the use of code formatting:
8
Q: Is using `code` styling for non-code samples okay?

AbhimanyuThe code is for code samples, of course. Its actual description is "a piece of program instructions." If package-names or date-and-time (technical details) are program instructions, then so are keyboard keys, graphic input, changes in settings, etc., because a computer can read them too. In fact...

discussion editing
 
Braiam
Braiam
more to the point:
But it makes the stuff I want people to read, more prominent... — Braiam Jul 3 at 1:34
 
jimmij
jimmij
1:39 PM
I rarely read meta, didn't know being mod is so beneficial, people stay in queue long time before election: meta.unix.stackexchange.com/questions/3573/…
 
 
2 hours later…
Braiam
Braiam
3:35 PM
@derobert does picard 1.3.2 works for you?
 
Braiam
Braiam
4:01 PM
so, moving .config/Musicbrainz directory works, I wonder why...
 
 
3 hours later…
Braiam
Braiam
7:17 PM
@slm the problem with the unordered list was that you didn't have a single empty line before it spec.commonmark.org/0.21/#bullet-list-marker
 

« first day (1751 days earlier)      last day (3209 days later) »