From: Nathan Trapuzzano <nbtrap@nbtrap.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15747@debbugs.gnu.org
Subject: bug#15747: Patch to optionally display raw bytes in hexadecimal
Date: Tue, 29 Oct 2013 13:18:26 -0400 [thread overview]
Message-ID: <87r4b49esd.fsf@nbtrap.com> (raw)
In-Reply-To: <83vc0gdnej.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 Oct 2013 18:58:44 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> For some "symmetry" with read-quoted-char-radix, perhaps make the name
> something like display-raw-bytes-radix, and make the feature accept
> the same values (i.e., 8. 10, and 16).
How do you suppose decimal escapes should be displayed so as to be
distinguishable from octal escapes? Left-padding them with 0s, which
typically indicates octal, seems like a bad idea; not padding them at
all would result in variable-width escapes, which seems like another bad
idea; and finally, many decimal escapes with three significant digits,
e.g. "\255", look like they may as well be octal.
The benefit to the way the hex escapes are implemented is that (1) they
are distinguishable from octal, thanks to the leading "x"; and (2) a
given hex escape sequence is the same width as its corresponding octal
escape, e.g. "\017" and "\x0F". I don't see how these properties could
be retained with decimal escapes.
next prev parent reply other threads:[~2013-10-29 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 13:52 bug#15747: Patch to optionally display raw bytes in hexadecimal Nathan Trapuzzano
2013-10-29 16:58 ` Eli Zaretskii
2013-10-29 17:18 ` Nathan Trapuzzano [this message]
2013-10-30 1:52 ` Stefan Monnier
2013-10-30 3:47 ` Eli Zaretskii
2013-10-30 3:54 ` Stefan Monnier
2013-10-30 10:33 ` Nathan Trapuzzano
2013-10-31 16:15 ` Eli Zaretskii
2013-11-01 1:10 ` Nathan Trapuzzano
2013-11-14 3:09 ` Nathan Trapuzzano
2013-11-14 4:52 ` Stefan Monnier
2016-02-24 3:58 ` Lars Ingebrigtsen
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=87r4b49esd.fsf@nbtrap.com \
--to=nbtrap@nbtrap.com \
--cc=15747@debbugs.gnu.org \
--cc=eliz@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).