emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Tom Alexander <tom@fizz.buzz>
Cc: emacs-orgmode@gnu.org
Subject: Re: Keyword becoming a paragraph based on optval
Date: Thu, 12 Oct 2023 18:18:11 +0000	[thread overview]
Message-ID: <875y3bd7rw.fsf@localhost> (raw)
In-Reply-To: <36bb93d2-53cc-48f5-ac15-2ea1c0516328@app.fastmail.com>

"Tom Alexander" <tom@fizz.buzz> writes:

> Emacs version: 29.1
> Org-mode version: f3de4c3e041e0ea825b5b512dc0db37c78b7909e (latest in git)
>
> This test document parses as a keyword:
> ```
> #+CAPTION[*foo*]: baz
> ```
>
> but this test document parses as a paragraph:
> ```
> #+CAPTION[*foo* bar]: baz
> ```

Expected. In the first case,
KEY = CAPTION[*foo*]
and VALUE = baz

In the second case, keyword does not match, because KEY cannot have
spaces.

https://orgmode.org/worg/org-syntax.html#Keywords

Note that _affiliated keyword_ has an optional form of

#+KEY[OPTVAL]: VALUE

where OPTVAL can have spaces.

But isolated #+CAPTION cannot be an affiliated keyword, which is why you
see what you see.

Whether we should allow OPTVAL in ordinary keywords has been discussed ,
and we might do it to simplify things at some point. But the rules are
like the above for now.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-10-12 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 18:04 Keyword becoming a paragraph based on optval Tom Alexander
2023-10-12 18:18 ` Ihor Radchenko [this message]
2023-10-12 18:18   ` Tom Alexander

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=875y3bd7rw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=tom@fizz.buzz \
    /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).