unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: cyd@stupidchicken.com, ihs_4664@yahoo.com, emacs-devel@gnu.org
Subject: Re: [wenbinye@gmail.com: hexl-max-address in hexl-mode is incorrect]
Date: Tue, 28 Nov 2006 09:48:45 +0900	[thread overview]
Message-ID: <E1Gor9R-0000yX-De@etlken.m17n.org> (raw)
In-Reply-To: <49866.128.165.123.18.1164654589.squirrel@webmail.lanl.gov> (herring@lanl.gov)

In article <49866.128.165.123.18.1164654589.squirrel@webmail.lanl.gov>, "Stuart D. Herring" <herring@lanl.gov> writes:

>>> How about: (- (position-bytes (point-max)) (position-bytes (point-min)))
> >
> > I already looked in this, and couldn't find a way to get it to work.
> > Hexl mode works by passing the buffer contents to an external program,
> > lib-src/hexl; thus, the byte values seen by hexl-mode depend on
> > buffer-file-coding-system.  The value of position-bytes is independent
> > of this.

> Is there some other coding system variable that does affect position-bytes
> (which we could then let-bind), or is it based on Emacs' internal,
> invariant encoding?

The latter.  The byte sequence of a buffer after decoded is
always in emacs-mule (in emacs-unicode-2 branch, it's
utf-8).  So, changing buffer-file-coding-system or any other
coding-system-related variables doesn't affects
position-bytes.

---
Kenichi Handa
handa@m17n.org

      reply	other threads:[~2006-11-28  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19  7:59 [wenbinye@gmail.com: hexl-max-address in hexl-mode is incorrect] Richard Stallman
2006-11-22 16:02 ` Chong Yidong
2006-11-22 16:59   ` Chong Yidong
2006-11-22 17:15   ` Kevin Rodgers
2006-11-22 22:02     ` Chong Yidong
2006-11-27 19:09       ` Stuart D. Herring
2006-11-28  0:48         ` Kenichi Handa [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=E1Gor9R-0000yX-De@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=ihs_4664@yahoo.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).