From: Manish <mailtomanish.sharma@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>, emacs-orgmode@gnu.org
Subject: Re: Re: Fix Subtle Heading Creation Bugs
Date: Sat, 18 Oct 2008 23:29:24 +0530 [thread overview]
Message-ID: <e7cdbe30810181059n5b5251eaw31f91f8444b5119a@mail.gmail.com> (raw)
In-Reply-To: <m2ljwm6i4j.fsf@pmade.com>
On Sat, Oct 18, 2008 at 8:54 PM, Peter Jones wrote:
> Carsten Dominik writes:
>> I am not so sure about forcing headline creation even when in a plain
>> list item. I can see why you would want it like this. However, the
>> reason for the current behavior is that then you can use the respect-
>> content function as a full replacement for M-RET, without the need to
>> always switch back and force between the two commands.
>>
>> Any thought about this?
>
> My position is that I want both features, and I have two key bindings,
> so it's a perfect match.
>
> The way I work is that I use C-RET for creating headings, and M-RET for
> creating plain lists. I never use M-RET for creating headings because I
> don't like how it creates the heading above the body of the current
> item.
>
> I could set org-insert-heading-respect-content to t, but it makes more
> sense in my head that M-RET is for plain lists, and C-RET is for
> headings.
>
> Before my patch, C-RET and M-RET only differed in where the heading was
> created (before or after the body). But the original behavior of
> OrgMode was that M-RET in a plain list created a new plain list item,
> while C-RET in a plain list would create a new heading.
>
> However, this could all be chalked up to me being lazy. I could just as
> easily do this in a plain list instead: RET C-RET. Well, except that
> with my patch, C-RET will create a new heading, even if point is in a
> drawer or something like a clock line. In that case I could do C-u
> C-RET.
>
> I just like the path of least resistance for creating new headings,
> C-RET. If this isn't good for OrgMode in general, I can easily bind C-j
> to do what I want as well.
I liked Peter's description, tried his patch and find C-Ret and M-Ret
behaviour better now. Earlier C-Ret and M-Ret had same effects (in my
setup) but makes better sense (to me) after the patch. Just a humble
opinion.
--
Manish
next prev parent reply other threads:[~2008-10-18 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 0:10 [PATCH] Fix Subtle Heading Creation Bugs Peter Jones
2008-10-18 6:01 ` Carsten Dominik
2008-10-18 15:24 ` Peter Jones
2008-10-18 17:59 ` Manish [this message]
2008-10-22 6:02 ` [PATCH] " Carsten Dominik
2008-10-23 0:30 ` Peter Jones
2008-10-23 5:07 ` 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=e7cdbe30810181059n5b5251eaw31f91f8444b5119a@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--cc=dominik@science.uva.nl \
--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).