RFC 1855, Netiquette Guidelines[1], specifies underscore for underlining. However, it says asterisks are for emphasis, not bold, per se. They just happened to (often?) display as bold because italics in terminals weren't a common thing. For the same reason, using /'s for italics didn't make much sense except maybe in word processors. I also suspect underscore become conflated with asterisk because some people preferred using the former for emphasis--people weren't usually trying to adhere to professional styling guides, and some people may have preferred underlining to impart emphasis, or just got into the habit without thinking about it.
replyI don't know how well RFC 1855 reflected common practice, though. It might be worthwhile to check the rendering code in clients like tin and mutt.
Since this seems to boil down to personal choice, has anyone considered a customisable alternative? Like a frontmatter that declares which character is bold, which is italic. You could easily convert between them according to local preference, much like tabs/spaces.
replyMy /usr/bin/ folder wants to know which bit gets italicised :)
replyI know this is a throwaway joke, but I was interested anyway...
replyAccording to my own local Markdown formatters, the answer would be both "usr" and "bin", with the surrounding slashes removed, but the internal slash remaining. In other words:
usr/bin
(but underlined instead of italic!)
Of course, this problem is nothing new since a filename might easily be named `_my_file_`.
Same as in my_snake_case_name :)
replyOrg mode uses / as well.
reply