From: Robert Cochran <robert+Emacs@cochranmail.com>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: 27122@debbugs.gnu.org
Subject: bug#27122: 26.0.50; [PATCH] Add customizable to display unprintables as hex
Date: Mon, 29 May 2017 11:46:03 -0700 [thread overview]
Message-ID: <87y3tfqz6c.fsf@SoraLaptop> (raw)
In-Reply-To: <20170529062859.mwoveygr5oh5iphz@odonien.localdomain> (Vasilij Schneidermann's message of "Mon, 29 May 2017 08:28:59 +0200")
Vasilij Schneidermann <v.schneidermann@gmail.com> writes:
> [...] Generally it seems that the world has moved on and prefers
> hexadecimal over octal formatting, except for `chmod` and Emacs. You
> sigh and convert the octal to hexadecimal. [...] Why can't Emacs make
> this easier?
Agreed. This makes Emacs really look like the odd man out. Personally,
chmod gets a pass because the octal very cleanly maps to Unix
permissions. But it looks awkward when Emacs does it, especially when I
believe it to have no reason to do so.
>> We already have quite a few related features, and I wonder whether
>> you could simply use one of them.
>
> The only one I'm aware of you could use instead is to manipulate the
> display table. This allows for the same effect, but is problematic as
> there are other modes manipulating it, such as whitespace-mode. You'd
> therefore need to manipulate `standard-display-table' and
> `buffer-display-table' with an appropriate hook to cover all cases.
>
> I consider the patch to be a cleaner solution.
Not as well versed on these features that Eli is referring to, so I'm
less helpful here. However, what is wrong with adding what is clearly an
option, so it can be changed in one place and be done with it?
--
~Robert Cochran
GPG Fingerprint - E778 2DD4 FEA6 6A68 6F26 AD2D E5C3 EB36 4886 8871
next prev parent reply other threads:[~2017-05-29 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 20:42 bug#27122: 26.0.50; [PATCH] Add customizable to display unprintables as hex Vasilij Schneidermann
2017-05-29 2:33 ` Eli Zaretskii
2017-05-29 6:28 ` Vasilij Schneidermann
2017-05-29 18:46 ` Robert Cochran [this message]
2017-05-29 19:52 ` Eli Zaretskii
2017-05-29 20:20 ` Vasilij Schneidermann
2017-05-29 23:55 ` Robert Cochran
2017-05-30 0:11 ` npostavs
2017-05-30 0:47 ` Robert Cochran
2017-05-29 19:39 ` Eli Zaretskii
2017-05-29 20:15 ` Vasilij Schneidermann
2017-05-30 6:24 ` Eli Zaretskii
2017-05-30 8:16 ` Vasilij Schneidermann
2017-05-30 8:38 ` Eli Zaretskii
2017-06-01 17:05 ` Vasilij Schneidermann
2017-06-01 18:19 ` Eli Zaretskii
2017-05-30 12:06 ` npostavs
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=87y3tfqz6c.fsf@SoraLaptop \
--to=robert+emacs@cochranmail.com \
--cc=27122@debbugs.gnu.org \
--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 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).