unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Horsley <tom.horsley@ccur.com>
To: bug-gnu-emacs@gnu.org
Subject: Improving X selection?
Date: Fri, 12 Oct 2007 10:50:22 -0400	[thread overview]
Message-ID: <20071012105022.6c8b174a@tweety> (raw)

Anyone who attempts to interact with a mix of older (xterm for
instance) and newer (gtk apps) with emacs while doing cut &
paste operations has undoubtedly noticed the persistent problem
of never winding up with the selection you actually want (now
that we have some folks using CLIPBOARD and others using
PRIMARY). Yes, you can set x-select-enable-clipboard, but all
that does is invert the set of incorrect text you get back.

I have just implemented a quick hack (definitely not suitable
for prime time) to the x-cut-buffer-or-selection-value
function. This hack observes when there is more than one "new"
selection and goes ahead and pushes the new ones it isn't
planning to return to the caller onto the kill ring.

Suddenly, life is wonderful! If I notice the last yank just
pasted in the wrong selection, all I need to do is run a
yank-pop and like magic the selection I actually wanted
replaces the nasty one I didn't want :-).

My question is this: If I were to change the possible return
values for the interprogram-paste-function so that it is
allowed to return a list of strings, and I modified all the
callers so they could expect a list of strings, and I made the
whole list get pushed on the kill ring, would such a change
likely be accepted? Or is an interface change like that too
radical? (Or do people even like the idea at all? :-).




                 reply	other threads:[~2007-10-12 14:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20071012105022.6c8b174a@tweety \
    --to=tom.horsley@ccur.com \
    --cc=bug-gnu-emacs@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 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).