unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25196@debbugs.gnu.org, "Juri Linkov" <juri@linkov.net>,
	"積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#25196: mention how to see top or middle of each yank-pop
Date: Thu, 1 Aug 2019 07:54:11 -0700 (PDT)	[thread overview]
Message-ID: <44efa309-3e91-4080-9114-bb0e50669bdc@default> (raw)
In-Reply-To: <87o9190x8r.fsf@tcd.ie>

> FWIW, see some slightly related discussion in the following thread:
> 
> https://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00650.html

Yes.  Might as well add the enhancements of
`browse-kill-ring+.el' to that input/discussion:

* Option `browse-kill-ring-alternative-ring' is an
  alternative selection ring to use, in addition to
  the `kill-ring'.  You can customize the value to
  any ring of strings you like.

* `browse-kill-ring' lets you use either ring as the
  selection ring to browse and paste.  You can even
  use both rings, in different `browse-kill-ring'
  display buffers.  In such a buffer, `o' pops to the
  list for the other ring.

* If you also use library `second-sel.el' then, by
  default, the secondary selection ring is the
  alternative ring.

* You can customize the set of commands that are
  recognized as yank alternative yank commands.  The
  alternative yank commands are commands that yank
  using a different selection ring.

* Following a yank command or alternative yank command,
  `M-y' pops and yanks the appropriate type of selection.
  A prefix arg N chooses the Nth previous selection in
  the ring.

* Otherwise (not following a yank or alternative yank),
  `M-y' browses the current selection ring.  A prefix
  arg switches to the other selection ring.  If you
  are in a `browse-kill-ring' buffer, then `M-y'
  switches to the other ring even without a prefix arg.

* If there is no alternative selection ring then `M-y'
  either pops (following a yank) or browses (not
  following a yank) the `kill-ring'.

---

https://www.emacswiki.org/emacs/download/browse-kill-ring%2b.el





  reply	other threads:[~2019-08-01 14:54 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
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 [this message]
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=44efa309-3e91-4080-9114-bb0e50669bdc@default \
    --to=drew.adams@oracle.com \
    --cc=25196@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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).