unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: luangruo@yahoo.com, 65892@debbugs.gnu.org
Subject: bug#65892: 30.0.50; yank-media fails for clipboard selection that are wiped after being accessed
Date: Tue, 25 Jun 2024 15:59:31 +0300	[thread overview]
Message-ID: <86sex19o0c.fsf@gnu.org> (raw)
In-Reply-To: <87bk3pr63w.fsf@gmail.com> (message from Visuwesh on Tue, 25 Jun 2024 10:06:35 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  65892@debbugs.gnu.org
> Date: Tue, 25 Jun 2024 10:06:35 +0530
> 
> BTW, I would be happy if I can do the above copying/cutting files from
> _dired_ without resorting to xclip(1) to set non-STRING targets.  I
> tried to do it with the facilities offered by Emacs but failed to set
> _only_ the required target without other things like STRING.  The same
> happened when I tried to copy an image to the clipboard.  I would be
> happy to open a bug report or some such if you're interested.

Isn't this the expected behavior?  The application that sets the
clipboard data has no idea what the consumer might need or would want
to do with the data.  It could past the image, or it could take the
image's meta-data (STRING) and do something with it.  Or it could take
the image's file name and copy the file somewhere.  Or something else.
This is why it is customary to put all the relevant data types in the
clipboard, so that the consumers could take whatever they need.





  reply	other threads:[~2024-06-25 12:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 16:54 bug#65892: 30.0.50; yank-media fails for clipboard selection that are wiped after being accessed Visuwesh
2024-06-24  3:53 ` Visuwesh
2024-06-24 12:13   ` Eli Zaretskii
2024-06-24 13:46     ` Visuwesh
2024-06-25  3:45       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-25  4:36         ` Visuwesh
2024-06-25 12:59           ` Eli Zaretskii [this message]
2024-06-28  4:20             ` Visuwesh
2024-06-28  8:59               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-28 10:03                 ` Visuwesh

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=86sex19o0c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65892@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=visuweshm@gmail.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.
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).