From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Release: Org-mode 5.09 Date: Wed, 19 Sep 2007 02:49:58 +0200 Message-ID: <87y7f3v5qh.fsf@bzg.ath.cx> References: <200709181700.17786.zslevin@gmail.com> <572452f66890dd8ebca04908cbd33e29@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXnlW-00072I-5q for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 20:50:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXnlU-000720-Ot for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 20:50:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXnlU-00071x-Js for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 20:50:04 -0400 Received: from ug-out-1314.google.com ([66.249.92.170]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IXnlU-00025Y-6l for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 20:50:04 -0400 Received: by ug-out-1314.google.com with SMTP id m4so199907uge for ; Tue, 18 Sep 2007 17:50:03 -0700 (PDT) In-Reply-To: <572452f66890dd8ebca04908cbd33e29@gmail.com> (Carsten Dominik's message of "Tue, 18 Sep 2007 12:59:40 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Carsten Dominik writes: >> Priority cycling is a bit odd. When I use M-n to cycle, it turns >> from #C-> nil-> #C-> nil, and M-p will be #A->nil->#A->nil. > > I did it like this on purpose, because I wanted S-up to > immediately increase the priority. I would vote for something very simple: increases priority, decreases priority. : nil -> [#A] -> [#B] -> [#C] -> nil [#A] -> [#B] -> [#C] -> nil -> [#A] [#B] -> [#C] -> nil -> [#A] -> [#B] [...] : nil -> [#C] -> [#B] -> [#A] -> nil [#A] -> nil -> [#C] -> [#B] -> [#A] [#B] -> [#A] -> nil -> [#C] -> [#B] [...] I know it wouldn't be aware of the default priority, but I would still prefer this behavior over another one. For making the priority setting aware of the default priority I would better use this: : increase priority (by with normal cycling) : switch default priority / nil But I still prefer the very simple interface... as I tend to think priority handling should be as smooth (and sober) as possible. -- Bastien