From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: Highlighting bug with org-agenda-set-restriction-lock Date: Sun, 07 Apr 2013 16:05:24 +0200 Message-ID: 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 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UOqBu-0007Hq-T6 for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 10:03:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UOqBs-0006EX-B9 for emacs-orgmode@gnu.org; Sun, 07 Apr 2013 10:03:30 -0400 In-reply-to: <87bo9qu4qq.fsf@bzg.ath.cx> 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: Bernt Hansen , emacs-orgmode@gnu.org, Carsten Dominik Didn't `M-RET' on an ordinary line of text also turn that line into a heading, about the same as doing `C-c *' on that line? At least with point in the first column (not sure about other cases)? My memory may be faulty, but lately I've found myself trying to do that, and scratching my head that it's not working as I thought it did. (I agree, of course, that the current behavior agrees with the docs, and that the behavior I seem to remember was redundant, but I also seem to remember it as pretty handy.) Yours, Christian Bastien writes: > Hi Bernt, > > Bernt Hansen writes: > >> Org file has this >> >> ,---- >> | * One >> | two >> | three >> | four >> | five >> `---- >> >> Put the cursor on first column of line two and hit M-S-RET gives me this >> >> ,---- >> | * One >> | two >> | * TODO >> | three >> | four >> | five >> `---- > > Okay, I see this too. > >> It seems to work correctly when there is no heading above the text >> (ie. One is not a headline) > > That's what I tested after your previous email, yes. > > 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! > > Thanks,