From: Nick Dokos <nicholas.dokos@hp.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug in behavior of M-RET with latest Org-mode
Date: Mon, 25 Feb 2013 00:39:05 -0500 [thread overview]
Message-ID: <14474.1361770745@alphaville> (raw)
In-Reply-To: Message from "John Wiegley" <johnw@newartisans.com> of "Sun, 24 Feb 2013 22:25:41 CST." <m2d2vp3tq2.fsf@newartisans.com>
John Wiegley <johnw@newartisans.com> wrote:
> In Org I've liked that fact that hitting M-RET in a list of headlines which
> have no intervening whitespace, will add a new headline without whitespace.
> Example:
>
> * One
> * Two<cursor>
> * Three
>
> If hit M-RET at the <cursor>, I'll would get:
>
> * One
> * Two
> * <cursor>
> * Three
>
> With the latest Org, I get:
>
> * One
> * Two
> * <cursor>
>
> * Three
>
> Is this just a regression, or has the core behavior been changed to do this?
> Is there a new variable I need to tweak to get the old behavior?
>
Actually, with the default (`auto') setting of the variable I indicated
in my previous email (`org-blank-before-new-entry'), I get the first
behavior, not the second.
The only problem is that when I insert the first headline, it gets
inserted after an empty first line, so adding a second headline fools
the auto setting into thinking I want empty lines between headings. But
if I delete the empty first line, M-RET never puts any empty lines between
headings. So the heuristic might not be perfect, but it seems to work for
all but the first headline.
Nick
next prev parent reply other threads:[~2013-02-25 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 17:41 Problem with org-babel and shell scripts John Wiegley
2012-07-10 20:08 ` Bastien
[not found] ` <johnw@newartisans.com>
2012-07-10 18:53 ` Nick Dokos
2013-02-25 5:13 ` Bug in behavior of M-RET with latest Org-mode Nick Dokos
2013-02-25 5:39 ` Nick Dokos [this message]
2013-03-03 17:07 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2013-02-25 4:25 John Wiegley
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=14474.1361770745@alphaville \
--to=nicholas.dokos@hp.com \
--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).