unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Manuel Giraud via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: orzodk <orzodk@fastmail.com>
Cc: Manuel Giraud via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: multiple kill and paste from X clipboard
Date: Fri, 12 Jan 2024 22:32:47 +0100	[thread overview]
Message-ID: <87il3yqlts.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <m2v87ygvla.fsf@blahblah.localdomain> (orzodk@fastmail.com's message of "Fri, 12 Jan 2024 13:12:01 -0700")

orzodk <orzodk@fastmail.com> writes:

> Manuel Giraud via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>
>> Hi,
>>
>> I'd like to be able to paste a serie of strings from Emacs to an
>> external X program (e.g. a form with multiple entry in a web browser).
>>
>> I could put all the strings in the Emacs' kill-ring but then a paste in
>> the other program will just retrieve the last killed string.  Or maybe,
>> Emacs could be informed that the last kill was paste externally and then
>> proceed to kill the next item?
>>
>> How could I do that?
>
> This is a limitation of X not Emacs. Each time you kill a value Emacs
> will put it into X's clipboard overwriting the previous value. A
> clipboard manager will help with this by keeping the history around. I
> personally use clipmenu but there are several tools to choose from. I
> also bind C-M-v in the window manager to the command to display the
> manager's history.

Thanks.  I've never used a clipboard manager so maybe I should now.  I
wish I could have a simpler Emacs only solution for this.  I thought
that maybe Emacs could be aware when the content is get from the primary
selection or the clipboard.
-- 
Manuel Giraud



      reply	other threads:[~2024-01-12 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:35 multiple kill and paste from X clipboard Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-12 15:49 ` Eli Zaretskii
2024-01-12 16:58   ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-12 19:49     ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-13  0:42     ` Po Lu
2024-01-13 10:08       ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-14 15:58       ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-14 22:45         ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-01-15 14:09           ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-17 14:52             ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-31 19:27               ` Stefan Monnier
2024-02-02 15:58                 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-02-02 16:54                   ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-01-12 20:12 ` orzodk
2024-01-12 21:32   ` Manuel Giraud via Users list for the GNU Emacs text editor [this message]

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=87il3yqlts.fsf@ledu-giraud.fr \
    --to=help-gnu-emacs@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=orzodk@fastmail.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.
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).