unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@jidanni.org>
Subject: Re: show binary in hexidecimal not octal
Date: Thu, 04 Jan 2007 02:32:24 +0800	[thread overview]
Message-ID: <8764bo0xmv.fsf@jidanni.org> (raw)
In-Reply-To: emubgs$sbq$1@sea.gmane.org

Do (compile "perl -e 'for(0..99999){print chr}' 2>&-" nil)

I see ^@^A^B...^Z^[^\^]^^^_ !"#$%&'()*+,-./01...wxyz{|}~^?
\200\201\202\203\204...\374\375\376\377 then Unicode etc.

I am happy with what I see, except that I want the octal shown in hex
instead. I.e. I am only unhappy about \200...\377.

Kevin> (setq buffer-display-table ...

I believe the solution instead lies in a new variable that controls a
deeper down C code item, without the user needing to fiddle with
buffer-display-table nor standard-display-table etc.

No need to target any specific characters, all I am saying is deep
down when emacs feels the urge to send a octal representation to the
screen, it sends instead a hex representation.

I am saying "emacs old buddy, you are doing a perfect job at selecting
what bytes or characters or whatever to send to the screen as (the
four byte) \222, etc. Now just allow the user the choice of how he
wants them shown: hex, octal (current), binary, decimal, etc."

Also there should be a way to paste the e.g., \222 that we see into another
buffer as the four bytes, not one, without having to resort to emacs
-nw and the mouse.

(By the way (compile "perl -e 'for(0..99999){print chr}' 2>&-" nil)
causes error in process filter: font-lock-fontify-keywords-region:
Stack overflow in regexp matcher. Probably for good reason. But that
is not what I'm worried about here.)

      reply	other threads:[~2007-01-03 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-25 20:25 show binary in hexidecimal not octal Dan Jacobson
2006-12-27 17:45 ` Kevin Rodgers
2007-01-03 18:32   ` Dan Jacobson [this message]

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=8764bo0xmv.fsf@jidanni.org \
    --to=jidanni@jidanni.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).