From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Christian Heinrich <christian@gladbachcity.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Possible bug in subtree matching with empty title + tags
Date: Sat, 02 May 2020 15:23:46 +0200 [thread overview]
Message-ID: <87a72q79nh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <03f1df447c14a414a4eb143b7055fed3f6afb234.camel@gladbachcity.de> (Christian Heinrich's message of "Sat, 02 May 2020 14:49:35 +0200")
Hello,
Christian Heinrich <christian@gladbachcity.de> writes:
> I'm often using empty header titles that only contain tags, such as
>
>> ** :foo:
>
> In my case, this is sufficient (for instance for flashcards, where I never have to actually have to
> use the agenda etc.). However, since Nicolas's refactoring in
> be31a0c4595a6d68b03b5cfbcbcdbf2cd76d2b7f empty titles seem to be prohibited. In the above example,
> using subtrees (C-/ m) on the "foo" tag will return nothing, even though the tag is in the file. Is
> this a deliberate change? I didn't see a note in the manual saying that headings must not be empty
> (this might be useful then).
This is not totally about empty headings, which are fine in Org.
Your example is ambiguous. Is it an empty headline with tags, or
a headline titled ":foo:" with no tag? Since we cannot support both,
choosing one breaks support for the other. You could use, e.g.,
a NO-BREAK SPACE character in your headline and lift the ambiguity.
This is not a change, but rather and undefined corner-case. There was
a discussion about it a couple of years ago, IIRC. I don't remember what
the outcome was.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2020-05-02 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 12:49 Possible bug in subtree matching with empty title + tags Christian Heinrich
2020-05-02 13:23 ` Nicolas Goaziou [this message]
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=87a72q79nh.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=christian@gladbachcity.de \
--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).