From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Release: Org-mode 5.09
Date: Wed, 19 Sep 2007 02:49:58 +0200 [thread overview]
Message-ID: <87y7f3v5qh.fsf@bzg.ath.cx> (raw)
In-Reply-To: <572452f66890dd8ebca04908cbd33e29@gmail.com> (Carsten Dominik's message of "Tue, 18 Sep 2007 12:59:40 +0200")
Carsten Dominik <carsten.dominik@gmail.com> 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:
<S-up> increases priority, <S-down> decreases priority.
<S-up> : nil -> [#A] -> [#B] -> [#C] -> nil
[#A] -> [#B] -> [#C] -> nil -> [#A]
[#B] -> [#C] -> nil -> [#A] -> [#B]
[...]
<S-down> : 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:
<S-up> : increase priority (by with normal cycling)
<S-down> : 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
next prev parent reply other threads:[~2007-09-19 0:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 10:35 Release: Org-mode 5.09 Carsten Dominik
2007-09-15 21:25 ` Rainer Stengele
2007-09-17 12:24 ` Carsten Dominik
2007-09-18 1:00 ` Xavier Maillard
2007-09-18 9:00 ` Levin
2007-09-18 10:59 ` Carsten Dominik
2007-09-19 0:49 ` Bastien [this message]
2007-09-20 8:45 ` Carsten Dominik
2007-09-20 8:45 ` Carsten Dominik
2007-09-20 13:34 ` Bastien
2007-09-20 14:08 ` Nuutti Kotivuori
2007-09-20 14:23 ` Bernt Hansen
2007-09-20 20:07 ` John Wiegley
2007-09-20 14:36 ` Bastien
2007-09-24 9:33 ` Rick Moynihan
2007-09-18 9:27 ` Levin
2007-09-18 11:01 ` Carsten Dominik
2007-09-18 9:38 ` Levin
2007-09-18 11:11 ` 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=87y7f3v5qh.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).