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: Sat, 30 Apr 2016 07:22:24 -0800 (GMT-08:00) [thread overview]
Message-ID: <97b12715-80de-40cb-9323-fe56cbc7c1bc@default> (raw)
In-Reply-To: <87vb2zz8nf.fsf@web.de>
> > 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).
>
> (Do you mean M-n, M-p?)
Yes, sorry.
> Internally it's just one list AFAIK (with the starting point somewhere
> in the middle after defaults have been added, so to say). M-n and M-p
> move through the complete list without distinguishing in which "part" we
> are - history or defaults. So I don't think just going to the end of
> the defaults would be confusing.
As I say, it would be fine by me.
And yes it is one list, and no, there is no distinguishing
the parts (perhaps there should be). Still the two parts
are different.
prev parent reply other threads:[~2016-04-30 15:22 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
2016-04-30 10:35 ` Michael Heerdegen
2016-04-30 15:22 ` Drew Adams [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97b12715-80de-40cb-9323-fe56cbc7c1bc@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).