From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Highlighting bug with org-agenda-set-restriction-lock Date: Sun, 07 Apr 2013 08:08:56 -0400 Message-ID: <87mwtaee5j.fsf@norang.ca> References: <87bo9tyvdj.fsf@norang.ca> <890D099A-90BD-4AA5-AD86-E145AF8429A7@gmail.com> <8738v5yqzz.fsf@norang.ca> <87vc7z8km3.fsf@bzg.ath.cx> <87a9pbxsum.fsf@norang.ca> <87bo9r73ne.fsf@bzg.ath.cx> <87r4indvzc.fsf@norang.ca> <87bo9qu4qq.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UOoP7-000344-85 for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 08:09:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UOoP5-0001DP-Kd for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 08:09:01 -0400 In-Reply-To: <87bo9qu4qq.fsf@bzg.ath.cx> (Bastien's message of "Sun, 07 Apr 2013 09:33:51 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org, Carsten Dominik Bastien 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