From: Pip Cet <pipcet@gmail.com>
To: Prateek Mehta <prateekmehta.in@gmail.com>, emacs-orgmode@gnu.org
Cc: mail@nicolasgoaziou.fr
Subject: Re: beamer_env tag issue with empty headlines
Date: Fri, 21 Aug 2015 17:37:27 +0000 [thread overview]
Message-ID: <CAOqdjBcN2gySb=C3h7-tDvhG_vvCV2VUQg74ejKvZftAa-AFQg@mail.gmail.com> (raw)
In-Reply-To: <87r3mzaanp.fsf@nicolasgoaziou.fr>
On 8/19/15, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Prateek Mehta <prateekmehta.in@gmail.com> writes:
>
>> That probably makes sense, though I still feel it is a little
>> inconsistent.
>> One could argue that anything within colons is an org tag (regardless of
>> whether the title is empty), and isn't meant to be exported. It's
>> probably
>> rare to start a headline with a colon anyway.
>>
>> Plus, I guess you are still somewhat restricted if you want to export a
>> headline ** foo :bar:, where :bar: is not a tag. ;)
>
> Of course, there are limitations (and workarounds) in each case.
>
> This is why I suggest to stay away from the "empty headlines + tags".
> The only empty headline supported in Org is the one without anything.
Could you explain your reasoning for this in some more detail? I use
empty headlines + tags (properties, actually) in my "set properties in
headlines rather than special drawers" code, and I wouldn't want it to
break even more than it currently is because of this limitation.
As you say, there are limitations in both cases, but do you actually
see headlines beginning with a colon being useful anywhere? I don't,
but empty headlines are useful for setting tags (or, in my case,
properties) without making up a title, so in my humble opinion it's a
clear-cut case to support empty headlines + tags.
next prev parent reply other threads:[~2015-08-21 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 3:11 beamer_env tag issue with empty headlines Prateek Mehta
2015-08-18 12:43 ` Suvayu Ali
2015-08-19 8:56 ` Nicolas Goaziou
2015-08-19 9:18 ` Prateek Mehta
2015-08-19 9:29 ` Nicolas Goaziou
2015-08-21 17:37 ` Pip Cet [this message]
2015-08-27 18:53 ` Nicolas Goaziou
2015-08-27 21:42 ` Pip Cet
2015-08-19 22:38 ` Rafael
2015-08-20 1:22 ` Nicolas Goaziou
2015-08-20 17:15 ` Rafael
2015-08-21 11:51 ` Nicolas Goaziou
2015-08-21 16:43 ` Rafael
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 22:01 Prateek Mehta
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='CAOqdjBcN2gySb=C3h7-tDvhG_vvCV2VUQg74ejKvZftAa-AFQg@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=prateekmehta.in@gmail.com \
/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).