This question already has an answer here:

Why am I seeing people marking technical parts of texts (names of functions, files) a code (e.g. `explorer.exe`), while logically it is not a code? I agree that these things should be somehow highlighted, but I don't see the code marking an appropriate way of doing it.

marked as duplicate by ShaWiz discussion Nov 2 '14 at 18:22

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • @shadowwizard Not a strict duplicate, the pinned question discusses emphasis, while this one criticises using inline code for technical names and names with specific format. – IllidanS4 Nov 2 '14 at 18:38
  • 1
    Well, the answers in both are quite the same. – ShaWiz Nov 2 '14 at 18:49

You are totally right. Code formatting shouldn't be use for anything but code. It's the best to edit it out if you possibly can. (I can stretch the definition of 'code' to 'computer instruction', so file paths could be in it too, if correctly used).

To answer your question why people use it: I think most of them see it as a tool to emphasize some parts of the post. Others think everything should be code formatted and even format the.

  • I agree with the accepted answer to the linked duplicate that code tags are also acceptable for "filenames, paths, API methods, commands, etc." – ThisSuitIsBlackNot Nov 2 '14 at 18:46
  • I can agree on that. In fact a file can be considered as computer instruction, so that would be in my definition of code. – Patrick Hofman Nov 2 '14 at 18:50
  • @Thi: updated the answer. – Patrick Hofman Nov 2 '14 at 18:53

Not the answer you're looking for? Browse other questions tagged .