URLs with underscores are displayed with org formatting

[paulbdavis]

When there are underscores in URLs or in other stuff (like request bodies, headers) org mode displays them as being a subscript

get /endpoint?page_size=99 turns into this:

[federicotdn]

Hey @paulbdavis

The docs for org-use-sub-superscripts mention this:

Still, ambiguity is possible. So when in doubt, use {} to enclose
the sub/superscript. If you set this variable to the symbol ‘{}’,
the braces are required in order to trigger interpretations as
sub/superscript. This can be helpful in documents that need "_"
frequently in plain text.

So maybe I could make verb-mode set buffer-locally this variable to {}, so that there's less chance of this happening (but may still happen if you do foo_{bar}). What do you think of that?

[buicaocuong9595]

Vào 25-01-2020 03:11, "Paul Davis" <[email protected]> đã viết:

When there are underscores in URLs or in other stuff (like request

bodies, headers) org mode displays them as being a subscript

…

get /endpoint?page_size=99 turns into this: — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[federicotdn]

Let's try to keep the conversation on-topic. Thanks.

[federicotdn]

As I want to avoid messing with users' Org configs, for the moment I recommend you use file-locals to set org-use-sub-superscripts to {}:

# Local Variables:
# org-use-sub-superscripts: {}
# End:

Hope it's useful!

[paulbdavis]

Yeah, the local variable solution works well. You may consider adding it to the README.

[federicotdn]

Good idea, thanks.