From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9406@debbugs.gnu.org
Subject: bug#9406: 24.0.50; Use M-p/M-n to navigate through the kill ring
Date: Thu, 01 Sep 2011 16:22:38 +0300 [thread overview]
Message-ID: <87mxeowg69.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0hM8y+=uSrJbyM0G85eWpo5LAFGk0-HHXL=YTk4Pap8Bg@mail.gmail.com> (Dani Moncayo's message of "Thu, 1 Sep 2011 11:13:09 +0200")
> So you want to keep the current behavior of "C-y M-y" for the sake of
> "traditional behavior", so that M-y would do one thing when preceded
> by C-y, and another one (completely different) when not.
There are many commands that work differently when preceded by another
key like e.g. `C-u'. So there is no problem when `M-y' preceded by `C-y'
works differently.
next prev parent reply other threads:[~2011-09-01 13:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 11:39 bug#9406: 24.0.50; Use M-p/M-n to navigate through the kill ring Dani Moncayo
2011-08-30 12:08 ` Juri Linkov
2011-08-30 12:17 ` Dani Moncayo
2011-08-30 12:27 ` Juri Linkov
2011-08-30 18:13 ` Deniz Dogan
2011-08-30 18:48 ` Dani Moncayo
2011-08-31 6:22 ` Dani Moncayo
2011-08-31 9:51 ` Juri Linkov
2011-08-31 10:45 ` Dani Moncayo
2011-08-31 13:01 ` Stefan Monnier
2011-08-31 13:55 ` Deniz Dogan
2011-08-31 14:33 ` Thierry Volpiatto
2011-08-31 14:52 ` Deniz Dogan
2011-09-02 0:39 ` Stefan Monnier
2011-08-31 15:40 ` Dani Moncayo
2011-08-31 15:45 ` Deniz Dogan
2011-08-31 16:11 ` Drew Adams
2011-08-31 15:33 ` Dani Moncayo
2011-08-31 15:47 ` David De La Harpe Golden
2011-08-31 16:36 ` Juri Linkov
2011-08-31 21:18 ` Dani Moncayo
2011-09-01 8:42 ` Juri Linkov
2011-09-01 9:13 ` Dani Moncayo
2011-09-01 9:53 ` Antoine Levitt
2011-09-01 10:28 ` Dani Moncayo
2011-09-01 13:22 ` Juri Linkov [this message]
2011-09-01 14:44 ` Dani Moncayo
2011-09-01 19:59 ` David De La Harpe Golden
2011-09-01 21:56 ` Dani Moncayo
2011-09-02 1:24 ` David De La Harpe Golden
2022-04-27 14:21 ` Lars Ingebrigtsen
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=87mxeowg69.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9406@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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).