unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25196@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#25196: mention how to see top or middle of each yank-pop
Date: Sat, 27 Jul 2019 17:30:42 -0700 (PDT)	[thread overview]
Message-ID: <e631e43f-18c0-4c79-86ba-ca91fc1239e3@default> (raw)
In-Reply-To: <87mugzw27n.fsf@mail.linkov.net>

> FWIW, here is battle-tested (i.e. use for many years) command
> that allows looking at the top or middle of each yank-pop before
> yanking:

I like it, including the fact that you can:
(1) edit a kill before pasting it, and even
(2) enter any text you want, for pasting.
#2 means this is not just about yanking kills.  

But please, if vanilla Emacs does this, do _not_
bind it to `C-M-y'.

This is a possible ~replacement (by users) for
`yank-pop'.  Users can bind it to `M-y'.  Or
if it becomes more popular someday than
`yank-pop' Emacs could give it binding `M-y'.

It's more or less a replacement for `yank-pop'
because the end effect is more or less the same:
yank something from the kill-ring (but see above).

Possible variants:

1. Prevent editing in the minibuffer (e.g.
   optionally), so you always get a kill (you
   can edit the text after yanking, of course).

2. While reading the string, force all kill
   commands to just delete, so that editing
   doesn't add to the kill-ring.

---

I use the secondary selection a lot, and have
keys for commands that use it.  I even have a
ring of secondary selections.  In many ways the
secondary selection is, or can be, parallel to
the region, and likewise its ring.

I use prefix `C-M-' for the secondary-selection
commands.

Yes, one user's/library's use of `C-M-y' isn't
reason enough to not waste that key on yet
another kill-ring yanker.  But the fact that
it's essentially a replacement for `yank-pop'
is a reasonable argument.

(`browse-kill-ring.el', for example, is another
such replacement.)





  reply	other threads:[~2019-07-28  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 19:06 bug#25196: mention how to see top or middle of each yank-pop 積丹尼 Dan Jacobson
2019-07-27 11:16 ` Lars Ingebrigtsen
2019-07-27 22:18   ` Juri Linkov
2019-07-28  0:30     ` Drew Adams [this message]
2019-07-28 10:06     ` Lars Ingebrigtsen
2019-07-28 11:06       ` Andreas Schwab
2019-07-28 13:33         ` Basil L. Contovounesios
2019-08-01 14:35       ` Basil L. Contovounesios
2019-08-01 14:54         ` Drew Adams
2019-08-01 21:12         ` Juri Linkov

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=e631e43f-18c0-4c79-86ba-ca91fc1239e3@default \
    --to=drew.adams@oracle.com \
    --cc=25196@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.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 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).