From: Titus von der Malsburg <email@example.com>
To: "Berry, Charles" <firstname.lastname@example.org>
Cc: Org mailing list <email@example.com>
Subject: Re: How to preserve empty headings
Date: Mon, 30 Nov 2020 19:14:12 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2020-11-30 Mon 18:31, Berry, Charles wrote:
>> On Nov 30, 2020, at 9:21 AM, Titus von der Malsburg <email@example.com> wrote:
>> When I start a new line with '* ' followed by RET, the space is automatically deleted and I’m left with a line that just has the asterisk (i.e. not a headline).
>> Unfortunately there are use cases where empty headlines make sense and they occur often in my work. One example is Beamer slides where each headline at some level produces a slide. If the user needs a slide without title (common, e.g., for a large images that fill the slide), an empty headline is needed.
>> Is there a way to teach Org to leave the empty headline intact?
>> I may be old-fashioned but when I type '* ', I do it for a reason and I wish that my text editor respects that. :)
> Instead of `* SPACE RET', try `* SPACE C-j'.
I’m aware of several workarounds and this one is perhaps the best. However, I’d prefer if RET would just work as expected. Org sometimes inserts extra material on RET which I think is okay (e.g. indentation), but is there any precedent, in Org or Emacs more broadly, for RET deleting text? It seems very counter-intuitive to me.
next prev parent reply other threads:[~2020-11-30 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 17:21 How to preserve empty headings Titus von der Malsburg
2020-11-30 17:31 ` Berry, Charles via General discussions about Org-mode.
2020-11-30 18:14 ` Titus von der Malsburg [this message]
2020-11-30 18:25 ` Diego Zamboni
2020-11-30 18:38 ` Titus von der Malsburg
2020-11-30 19:17 ` Tom Gillespie
2020-11-30 19:25 ` Diego Zamboni
2020-11-30 22:25 ` Berry, Charles via General discussions about Org-mode.
2020-11-30 19:20 ` Titus von der Malsburg
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).