all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 42384@debbugs.gnu.org, rms@gnu.org
Subject: bug#42384: octal escape sequences old fashioned
Date: Thu, 16 Jul 2020 18:14:26 +0200	[thread overview]
Message-ID: <m2lfjjsahp.fsf@gmail.com> (raw)
In-Reply-To: <87imeo2sh7.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Thu, 16 Jul 2020 08:50:28 +0800")

>>>>> On Thu, 16 Jul 2020 08:50:28 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:

    積丹尼> (info "(emacs) Text Display") says:
    積丹尼>       The raw bytes with codes ‘U+0080’ (octal 200) through ‘U+009F’ (octal
    積丹尼>    237) are displayed as “octal escape sequences”, with the ‘escape-glyph’
    積丹尼>    face.  For instance, character code ‘U+0098’ (octal 230) is displayed as
    積丹尼>    ‘\230’.  If you change the buffer-local variable ‘ctl-arrow’ to ‘nil’,
    積丹尼>    the ASCII control characters are also displayed as octal escape
    積丹尼>    sequences instead of caret escape sequences.

    積丹尼> OK but octal is rather old fashioned so the user should be given the
    積丹尼> choice of hex, etc.

    display-raw-bytes-as-hex is a variable defined in `C source code'.
    Its value is t
    Original value was nil

      You can customize this variable.
      This variable was introduced, or its default value was changed, in
      version 26.1 of Emacs.
      Probably introduced at or before Emacs version 26.1.

    Documentation:
    Non-nil means display raw bytes in hexadecimal format.
    The default is to use octal format (200) whereas hexadecimal (x80)
    may be more familiar to users.

(the manual in emacs-27 mentions this)

Robert





  reply	other threads:[~2020-07-16 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  0:50 bug#42384: octal escape sequences old fashioned 積丹尼 Dan Jacobson
2020-07-16 16:14 ` Robert Pluim [this message]
2020-07-16 16:42 ` Eli Zaretskii
2020-07-16 18:16   ` 積丹尼 Dan Jacobson
2020-07-17 14:42     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2lfjjsahp.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=42384@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=rms@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 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.