From: Bernt Hansen <bernt@norang.ca>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Highlighting bug with org-agenda-set-restriction-lock
Date: Sun, 07 Apr 2013 08:08:56 -0400 [thread overview]
Message-ID: <87mwtaee5j.fsf@norang.ca> (raw)
In-Reply-To: <87bo9qu4qq.fsf@bzg.ath.cx> (Bastien's message of "Sun, 07 Apr 2013 09:33:51 +0200")
Bastien <bzg@gnu.org> writes:
> I need to think harder about this and to get more feedback, because
> the new behavior seems the correct one to me. Also, it is in sync
> with the docstring of `org-insert-heading-respect-content':
>
> Non-nil means insert new headings after the current subtree. When
> nil, the new heading is created directly after the current line.
> ^^^^^
>
> This is about *inserting* a new heading, not about turning the current
> line into a heading (which is fine to have when there is no heading
> above, of course.) Also, reverting to the old behavior would move
> S-M-RET closer to C-c *.
>
> Let's see if other users find the current behavior annoying, and let
> me know how annoying it is to you!
OK. If this is working as designed I'm fine with that. I'll just
change my habits :) I actually didn't read the docstring was just
basing it on previous behaviour (which may have been incorrect).
Thanks,
Bernt
next prev parent reply other threads:[~2013-04-07 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 13:12 Highlighting bug with org-agenda-set-restriction-lock Bernt Hansen
2013-04-05 13:20 ` Bernt Hansen
2013-04-05 14:12 ` Carsten Dominik
2013-04-05 14:23 ` Carsten Dominik
2013-04-05 14:46 ` Carsten Dominik
2013-04-05 15:48 ` Bernt Hansen
2013-04-06 5:17 ` Carsten Dominik
2013-04-05 14:46 ` Bernt Hansen
2013-04-05 14:50 ` Carsten Dominik
2013-04-06 20:33 ` Bastien
2013-04-06 21:16 ` Bernt Hansen
2013-04-06 21:25 ` Bastien
2013-04-07 0:29 ` Bernt Hansen
2013-04-07 7:33 ` Bastien
2013-04-07 12:08 ` Bernt Hansen [this message]
2013-04-07 14:05 ` Christian Moe
2013-04-07 18:43 ` Bernt Hansen
2013-04-10 22:36 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mwtaee5j.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=bzg@gnu.org \
--cc=carsten.dominik@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.