From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-orgmode@gnu.org
Subject: Re: org-insert-heading rewritten from scratch
Date: Sat, 31 Aug 2013 16:34:45 +0200 [thread overview]
Message-ID: <877gf2nd2y.fsf@gmail.com> (raw)
In-Reply-To: <2CBE3492-5A45-48D6-AF3B-A81D0C322009@gmail.com> (Carsten Dominik's message of "Sat, 31 Aug 2013 16:00:56 +0200")
Hello,
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On 8.8.2013, at 09:41, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Hi,
>>>
>>> I have rewritten org-insert-heading, because it had become an unmaintainable beast.
>>> Please follow up in this thread if you find problems with the new implementation.
>>> Very likely there will be bugs, but now I am at least confident they can be fixed.
>>>
>>> - Carsten
>>
>> Awesome! Thanks very much for doing this. Will report back with bugs.
>
> I take it none have been found?
Not really a bug, but I find some behaviour surprising: when at a the
beginning of a regular text line, there is no way to create a headline
just above it. In the following example:
XCursor is at "X"
Neither M-RET, C-u M-RET, C-RET nor C-u C-RET can do it. Is it intended?
Also in this case, I think C-RET should create the new headline _after_
the subtree, since that's its whole point anyway, AFAIU.
Eventually, it seems that behaviour towards empty lines is a bit
unpredictable. In the following example, M-RET will be behave
differently on each blank line between Paragraph and "H2". C-RET will be
consistent. Note: I have `auto' as value for `heading' key in
`org-blank-before-new-entry'.
* H1
Paragraph
* H2
IMO, using M-RET and C-RET should be as smooth an experience as
possible.
I also suggest to write function specifications as tests in test-org.el.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-08-31 14:34 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 [this message]
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
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=877gf2nd2y.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).