unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Deniz Dogan <deniz@dogan.se>
Cc: 9406@debbugs.gnu.org
Subject: bug#9406: 24.0.50; Use M-p/M-n to navigate through the kill ring
Date: Tue, 30 Aug 2011 20:48:35 +0200	[thread overview]
Message-ID: <CAH8Pv0hdJgkjzcCD5vrKLu_bcPwRMEb68R2bsEwN-HyFgbY=Cg@mail.gmail.com> (raw)
In-Reply-To: <4E5D2849.4090107@dogan.se>

Hi Deniz,

On Tue, Aug 30, 2011 at 20:13, Deniz Dogan <deniz@dogan.se> wrote:
> I strongly oppose it.  I've used M-n and M-p for forward-paragraph and
> backward-paragraph for years and I'm sure many other people use them for
> other things too.  Please, leave M-n and M-p for other things than browsing
> the kill ring in this manner.

You (and many others) could still use M-n and M-p for whatever you
want, because my proposal would only affect that keys *just after
typing C-y, and before doing anything else*.

> There is already many different ways to do
> this, all on the Emacs Wiki.[1]

I'm interested in improving the standard GNU Emacs, and the current
way of navigating through the kill ring is not very convenient, as I
explained.  My proposal would greatly improve it without harming
anyone (IMO).

-- 
Dani Moncayo





  reply	other threads:[~2011-08-30 18:48 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 [this message]
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
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='CAH8Pv0hdJgkjzcCD5vrKLu_bcPwRMEb68R2bsEwN-HyFgbY=Cg@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=9406@debbugs.gnu.org \
    --cc=deniz@dogan.se \
    /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).