From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55870@debbugs.gnu.org, larsi@gnus.org, Bruce <brucelam1982pi@anche.no>
Subject: bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work
Date: Sun, 17 Jul 2022 15:27:12 +0800 [thread overview]
Message-ID: <87wnccfbcf.fsf@yahoo.com> (raw)
In-Reply-To: <83a698qm67.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 17 Jul 2022 09:37:52 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Maybe this is the reason. Po Lu, what data-type do we use on X to put
> data into the clipboard when the user presses M-w?
None in particular: we store the clipboard data locally, and other
programs request different selection "targets" from Emacs depending on
the coding system they want it in. Normally, it is UTF8_STRING for
UTF-8 data, COMPOUND_TEXT for X compound text data, STRING for
iso-latin-1, and C_STRING for raw text.
selection-coding-system should not be set under X, since the semantics
are very confusing. Simple example: when selection-coding-system is set
to utf-8-dos, Emacs will respond to requests for UTF8_STRING with text
encoded with utf-8-dos, but requests for STRING will still be Latin-1.
next prev parent reply other threads:[~2022-07-17 7:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 8:50 bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:57 ` Lars Ingebrigtsen
[not found] ` <1fc51cba-c767-2e5f-e0be-6e0f8d7d1df6@anche.no>
2022-06-10 12:44 ` Lars Ingebrigtsen
2022-07-11 11:01 ` Lars Ingebrigtsen
[not found] ` <92253b43-50a1-554e-de66-f31f0c423b1f@anche.no>
2022-07-12 12:11 ` Lars Ingebrigtsen
2022-07-13 3:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 10:56 ` Lars Ingebrigtsen
2022-07-13 11:12 ` Visuwesh
2022-07-13 11:43 ` Eli Zaretskii
2022-07-14 9:50 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:02 ` Lars Ingebrigtsen
2022-07-14 10:09 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:13 ` Eli Zaretskii
2022-07-15 12:44 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 13:03 ` Eli Zaretskii
2022-07-16 0:15 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-16 5:37 ` Eli Zaretskii
2022-07-17 2:38 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 6:37 ` Eli Zaretskii
2022-07-17 7:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-17 7:51 ` Eli Zaretskii
2022-07-17 8:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 10:08 ` Eli Zaretskii
2022-07-17 11:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 12:49 ` Eli Zaretskii
2022-07-17 13:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:27 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 1:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:24 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:16 ` Eli Zaretskii
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=87wnccfbcf.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55870@debbugs.gnu.org \
--cc=brucelam1982pi@anche.no \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).