From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 27270@debbugs.gnu.org, v.schneidermann@gmail.com,
npostavs@users.sourceforge.net
Subject: bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings
Date: Sat, 10 Jun 2017 10:24:25 +0300 [thread overview]
Message-ID: <83h8zo71au.fsf@gnu.org> (raw)
In-Reply-To: <2202b54b-606f-0a10-abf7-5cb1a9164897@cs.ucla.edu> (message from Paul Eggert on Fri, 9 Jun 2017 16:44:46 -0700)
> Cc: npostavs@users.sourceforge.net, 27270@debbugs.gnu.org,
> v.schneidermann@gmail.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 9 Jun 2017 16:44:46 -0700
>
> The idea is to add a new \X escape for character constants and strings. This
> escape would allow at most two hexadecimal digits, rather than the unlimited
> number of digits that \x does. For example, the Lisp string "\XABC" would be
> equivalent to the Lisp string "\xAB\ C", that is, it would be a two-character
> string containing the character U+00AB LEFT POINTING GUILLEMET followed by the
> character U+0043 LATIN CAPITAL LETTER C.
So your proposal would mean a change to the Lisp reader to support
such escapes, right? If so, isn't such a change
backward-incompatible?
> Also, display-raw-bytes-as-hex would cause raw bytes to be displayed with this
> new X escape, rather than with with the x escape.
It could only do that for codepoints below 256 decimal, so that
limitation should be taken into account when deciding on the proposal.
next prev parent reply other threads:[~2017-06-10 7:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 3:57 bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings Paul Eggert
2017-06-07 5:17 ` Eli Zaretskii
2017-06-08 0:49 ` Paul Eggert
2017-06-08 1:07 ` npostavs
2017-06-08 15:20 ` Eli Zaretskii
2017-06-08 15:56 ` Paul Eggert
2017-06-08 16:11 ` Eli Zaretskii
2017-06-08 16:24 ` Paul Eggert
2017-06-08 18:59 ` Eli Zaretskii
2017-06-08 19:43 ` Paul Eggert
2017-06-08 19:56 ` Eli Zaretskii
2017-06-08 20:35 ` Paul Eggert
2017-06-09 6:00 ` Eli Zaretskii
2017-06-09 23:44 ` Paul Eggert
2017-06-10 7:24 ` Eli Zaretskii [this message]
2017-06-11 0:04 ` Paul Eggert
2017-06-11 14:48 ` Eli Zaretskii
2017-06-11 17:26 ` Paul Eggert
2017-09-02 13:25 ` Eli Zaretskii
2022-04-23 14:00 ` Lars Ingebrigtsen
2022-04-24 7:10 ` Paul Eggert
2022-04-24 9:56 ` Vasilij Schneidermann
2022-04-24 10:26 ` Andreas Schwab
2022-04-24 10:51 ` Vasilij Schneidermann
2022-04-24 11:01 ` Andreas Schwab
2022-04-24 11:29 ` Lars Ingebrigtsen
2022-04-24 22:46 ` Paul Eggert
2022-04-24 11:24 ` Lars Ingebrigtsen
2022-04-24 22:35 ` Paul Eggert
2022-04-25 7:40 ` Lars Ingebrigtsen
2022-04-25 16:49 ` Paul Eggert
2022-04-26 10:06 ` Lars Ingebrigtsen
2022-04-26 16:48 ` Paul Eggert
2022-04-27 12:13 ` Lars Ingebrigtsen
2022-04-27 17:21 ` Paul Eggert
2022-04-27 17:22 ` Lars Ingebrigtsen
2022-04-28 17:58 ` Paul Eggert
2017-06-10 22:52 ` npostavs
2017-06-11 0:10 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8zo71au.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27270@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=npostavs@users.sourceforge.net \
--cc=v.schneidermann@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.