From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 13334@debbugs.gnu.org
Subject: bug#13334: 24.3.50; enhancement request: `C-0 M-n' reverses order of defaults
Date: Fri, 29 Apr 2016 15:47:19 -0700 (PDT) [thread overview]
Message-ID: <e4003669-8489-436c-a59a-522364583449@default> (raw)
In-Reply-To: <87h9ekcbsb.fsf@web.de>
> > The enhancement would be to let a zero prefix arg (e.g. `C-0') reverse
> > the list of available default values and then go to the first one
> > (previously the last one). So you could cycle among the defaults in the
> > opposite order.
>
> A slightly different approach would be to make it just go to the end of
> the history, without changing the order. Then you could just use M-p to
> go backwards. I guess that would not be hard to do (see
> `goto-history-element').
Agreed. That is about as good. (But again, it's not about the input
_history_. It's about a set of possible default values.)
The only reason what I suggested might be considered slightly better
is that `C-p' is generally thought of as accessing the input history
(see the above confusion), not the defaults.
That's the case at the outset, but of course once you've used one of
`C-n' or `C-p' the other just reverses within the list (inputs or
defaults) that you started cycling, until you get back to the starting
point (origin, dividing the two lists).
next prev parent reply other threads:[~2016-04-29 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 4:55 bug#13334: 24.3.50; enhancement request: `C-0 M-n' reverses order of defaults Drew Adams
2013-01-03 0:27 ` Juri Linkov
2013-01-03 0:49 ` Drew Adams
2013-01-03 23:51 ` Juri Linkov
2013-01-04 0:40 ` Drew Adams
2016-04-28 19:18 ` Lars Ingebrigtsen
2016-04-29 14:36 ` Drew Adams
2016-04-29 22:04 ` Michael Heerdegen
2016-04-29 22:47 ` Drew Adams [this message]
2016-04-30 10:35 ` Michael Heerdegen
2016-04-30 15:22 ` Drew Adams
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=e4003669-8489-436c-a59a-522364583449@default \
--to=drew.adams@oracle.com \
--cc=13334@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.