emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: c.buhtz@posteo.jp
To: Emacs orgmode <Emacs-orgmode@gnu.org>
Subject: Bug: Inconsistent behaviour about inline markup
Date: Sat, 14 Jan 2023 20:12:56 +0000	[thread overview]
Message-ID: <1e2ff20cefa09050e9e3c690701f83ed@posteo.de> (raw)

Hello,

I'm not sure if this is a bug or intended by design. Please point to the 
correct documentation if there is one.
I'm also not sure if Orgmode is the related component here or if there 
is any other?

What I describe is in the context of auto-formating markup in orgmode. 
When you type "=verb=" or "~code~" the first and last character 
disappears but the text gets another color. In GUI mode also "/" and "*" 
will disapear and make the word italic or bold.

What characters are allowed in front of the beginning inline marker 
("=", "~", "/", "*", etc) and after the ending marker.
Allowed may not be the correct word. With which characters is Orgmode 
still able to recognize the markup right.

Examples (the " are not part of the data)

  - "=verb=" -> OK, because line beginning and ending are allowed
  - "(=verb=)" -> OK
  - " =verb=}" -> OK. Space/blank and curly bracket allowed

- "=verb=\" -> OK. Backslash at the end.
- "\=verb=" -> BAD. Backslash in the beginning not allowed. No 
formatting happens.
- ")=verb=(" -> BAD. "inverted" brackets not allowed.
- "=verb=." ->OK. Dot at the end.
- ".=verb=" -> BAD. Dot at the beginning.

IMHO there shouldn't be a difference in the allowed characters in front 
of the beginning inline marker (the "=" here in the example) and the one 
after the ending inline marker.

First of all it would help me if this is documented somewhere.

Second it would improve my (regex) code (which have to parse such 
org-markup) and its maintainability if allowed characters would be 
uniform/consistent.

Kind
Christian


             reply	other threads:[~2023-01-14 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 20:12 c.buhtz [this message]
2023-01-15  6:22 ` Bug: Inconsistent behaviour about inline markup Timothy
2023-01-15 10:16   ` c.buhtz
2023-01-15 10:31     ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e2ff20cefa09050e9e3c690701f83ed@posteo.de \
    --to=c.buhtz@posteo.jp \
    --cc=Emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).