From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-pretest-bug@gnu.org, Kevin Rodgers <ihs_4664@yahoo.com>,
richard.stallman@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs puts binary junk into the clipboard, marking it as text
Date: Sat, 16 Sep 2006 19:25:20 +0200 [thread overview]
Message-ID: <450C3380.2050008@swipnet.se> (raw)
In-Reply-To: <450BE084.10905@swipnet.se>
Jan D. wrote:
> Kevin Rodgers wrote:
>> Jan Djärv wrote:
>>>
>>>
>>> Chris Moore skrev:
>>>> A very simple case which reproduces the bug:
>>>>
>>>>> I made a 1-byte file containing just character 0300 (octal),
>>>>> copied that using Emacs, and clipman started printing its error
>>>>> message over and over again.
>>>>
>>>>
> Anyway, I will fix this somehow, we should not be sending non-UTF8 as
> a UTF8_STRING.
I've checked in a fix that changes UTF8_STRING to STRING if the data
doesn't look like UTF8. However, this might give errors too. The only
way to be sure to copy raw binary data correctly is by adding a new type
(like application-specific/octet-stream). But if we do that, nobody
will be able to get data from Emacs, as such a type is not standard and
unsupported. Copy-paste with raw binary data is just something most
apps don't do.
Please try this, it is hopefully better.
Jan D.
next prev parent reply other threads:[~2006-09-16 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1158280855.14121.69.camel@chrislap.madeupdomain.com>
2006-09-15 7:07 ` Emacs puts binary junk into the clipboard, marking it as text Jan Djärv
2006-09-15 16:30 ` Kevin Rodgers
2006-09-16 11:31 ` Jan D.
2006-09-16 17:25 ` Jan D. [this message]
2006-09-19 5:05 ` Kenichi Handa
2006-09-19 6:15 ` Jan Djärv
2006-09-19 7:14 ` Kenichi Handa
2006-09-19 10:54 ` Stefan Monnier
2006-09-19 11:14 ` Kenichi Handa
2006-09-19 16:15 ` Stefan Monnier
2006-09-19 19:32 ` Jan D.
2006-09-20 2:20 ` Kenichi Handa
2006-10-19 7:19 ` Jan Djärv
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=450C3380.2050008@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=ihs_4664@yahoo.com \
--cc=richard.stallman@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).