emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-orgmode@gnu.org
Subject: Re: org-insert-heading rewritten from scratch
Date: Tue, 3 Sep 2013 16:04:35 +0200	[thread overview]
Message-ID: <2AD3F53E-C4C6-44D9-8D1E-6B47575780C9@gmail.com> (raw)
In-Reply-To: <87r4d62eig.fsf@gmail.com>


On Sep 3, 2013, at 3:58 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
> 
>> I am still not clear about this.  In your earlier mail you made this example:
>> 
>>> Well same as above: I think it eats blank lines where it shouldn't. It
>>> the following cases:
>>> 
>>> * H1
>>> 
>>> ** H2
>>> 
>>>    H
>>> X
>>> 
>>> and
>>> 
>>> * H1
>>> 
>>> * H2
>>> 
>>>   H
>>> 
>>> X  
>>> 
>>> I don't think there's any reason for M-RET to eat blank line before
>>> point with either `org-blank-before-new-entry' set to `auto' or t. It
>>> should know that a blank line is expected before the new entry and
>>> therefore should create the headline at point.
>> 
>> WIth `auto', there will be an empty line before the next entry in both
>> cases. In both cases it looks at the H2 headline and sees the empty
>> line before it. Are you saying the behaviour should be different in
>> both cases?
> 
> Yes, it should.
> 
> As you point out, in both cases the algorithm knows that there should be
> a blank line before the new entry (with the assumption that behaviour is
> set to `auto'). In the first case, if it inserts the headline at point,
> there will be none, so it has to add one. In the second case, there is
> no need to add one since creating it at point will fulfill the
> requirement (which is "a blank line before new headline").

Yes.  But you agree that the *result* should be the same, i.e. that there will
be an empty line before the newly inserted headline.

I think/hope we do agree now.

> 
> Re-reading myself, I agree that my quoted explanations are a bit
> confusing. I hope this should clarify my point.

I think so.

Thank you for your patience.

- Carsten

  reply	other threads:[~2013-09-03 14:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  6:43 org-insert-heading rewritten from scratch Carsten Dominik
2013-08-08  7:41 ` Eric Abrahamsen
2013-08-31 14:00   ` Carsten Dominik
2013-08-31 14:34     ` Nicolas Goaziou
2013-09-01  6:13       ` Carsten Dominik
2013-09-01  8:19         ` Nicolas Goaziou
2013-09-01 12:04           ` Carsten Dominik
2013-09-01 12:25             ` Nicolas Goaziou
2013-09-03 13:16             ` Nicolas Goaziou
2013-09-03 13:25               ` Carsten Dominik
2013-09-03 13:33                 ` Carsten Dominik
2013-09-03 13:38                 ` Nicolas Goaziou
2013-09-03 13:47                   ` Carsten Dominik
2013-09-03 13:58                     ` Nicolas Goaziou
2013-09-03 14:04                       ` Carsten Dominik [this message]
2013-09-03 14:12                         ` Nicolas Goaziou
2013-09-07 10:50                         ` Nicolas Goaziou
2013-09-07 12:01                           ` Nicolas Goaziou
2013-09-01  2:38     ` Eric Abrahamsen
2013-09-01  3:11     ` Samuel Wales
2013-09-01  3:13       ` Samuel Wales
2013-09-09 16:42 ` Michael Brand
2013-09-09 19:10   ` Nicolas Goaziou
2013-09-09 20:37     ` Michael Brand
2013-09-12 20:20       ` Carsten Dominik
2013-09-12 20:52         ` Michael Brand
2013-09-12 20:58           ` Carsten Dominik

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=2AD3F53E-C4C6-44D9-8D1E-6B47575780C9@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=n.goaziou@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).