all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Antoine Levitt <antoine.levitt@gmail.com>
To: 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 11:53:04 +0200	[thread overview]
Message-ID: <87hb4wvbb3.fsf@gmail.com> (raw)
In-Reply-To: <CAH8Pv0hB1Of8FhHdQxBCAwgddJVrd7L6+qUjEFHZPqz7ycaAFQ@mail.gmail.com>

01/09/11 11:13, Dani Moncayo
> On Thu, Sep 1, 2011 at 10:42, Juri Linkov <juri@jurta.org> wrote:
>>> WDYT?
>>
>> I think we should not change the traditional behavior of `C-y M-y M-y ...'
>> that many users are accustomed to.
>
> Sorry to hear that.  I agree that it is good to keep the traditional
> behavior as much as possible, but not at the expense of evolving
> positively.
>
>> What we could do is to activate the
>> minibuffer browsing the kill-ring on `M-y' (not preceded by `C-y').
>
> 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.  IMO, this
> mixing/overloading of functionality in M-y is not clean, and besides,
> one of those two tasks would be already implemented in M-p.  I'd like
> you to reconsider this, please.
>
>> And optionally bind `M-p'/`M-n' after `C-y' to more transient version
>> of the current `M-y' that doesn't require multiple undo (but still
>> you have to undo the first yank inserted by `C-y').
>
> 100% agreement on that (I like your "transient version" improvement).

What about the following UI?

M-y triggers a kind of kill-ring browsing: it opens a small buffer above
the minibuffer with the next killed text (that which would be inserted
by C-y), accessible with M-y or M-n. If the user presses M-y or M-n, the
buffer expands to display the previous killed text as well, accessible
with M-p. In any event, pressing RET inserts the current killed text to
the buffer, and pressing anything other than RET/M-y/M-n/M-p kills the
buffer and resumes normal editing.

C-y M-y directly jumps to the second step of the above, but inserts
automatically the current killed text, preserving backwards
compatibility.

Therefore, C-y M-y M-y ... does the right thing, with the added
convenience of a buffer allowing you to go back to a previous
completion. Also M-y becomes a nice alias for viewing the kill-ring.

This has the merit of not binding M-n / M-p in anything else than the
mode this buffer would be displayed in. Doing it any other way would
probably cause confusion to users/modes who bind M-n/M-p.

The appearance of the small window would be controllable with a boolean
setting.






  reply	other threads:[~2011-09-01  9:53 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hb4wvbb3.fsf@gmail.com \
    --to=antoine.levitt@gmail.com \
    --cc=9406@debbugs.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 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.