From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: dired doesn't work properly with a multibyte locale
Date: Sun, 12 Jan 2003 06:56:20 -0500 [thread overview]
Message-ID: <E18Xgiy-0004Op-00@fencepost.gnu.org> (raw)
In-Reply-To: <buok7hibyqd.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 06 Jan 2003 15:04:26 +0900)
It doesn't seem simple to get the byte offset information, so perhaps the
best thing to do is simply not use --dired if `file-name-coding-system' is
a multibyte encoding.
For the moment, this may be the best we can do. But that means the other bugs
that --dired was meant to fix come back. For the longer term, we need
a way to make --dired work properly with multibyte decoding in Emacs.
One idea is that decoding could optionally keep a record of every
place it changes the length of text. Most of the time, this optional
feature would be turned off, but dired would turn it on. The output
would be a list of elements of the form (POS . CHANGE) where POS is
the buffer position (or perhaps, position relative to the start of the
input), and CHANGE would be the change in size of the text at that
place. With all this information, it would be straightforward
to correct all the information provided by --dired.
Handa, do you think this would be feasible?
next prev parent reply other threads:[~2003-01-12 11:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 6:04 dired doesn't work properly with a multibyte locale Miles Bader
2003-01-11 20:00 ` Stefan Monnier
2003-01-11 20:16 ` Miles Bader
2003-01-12 11:56 ` Richard Stallman [this message]
2003-01-15 10:43 ` Kenichi Handa
2003-01-15 23:30 ` Richard Stallman
2003-01-23 4:31 ` Miles Bader
2003-01-23 6:02 ` Kenichi Handa
2003-01-23 6:12 ` Miles Bader
2003-01-25 0:49 ` Kenichi Handa
2003-01-27 4:17 ` Miles Bader
2003-01-27 5:01 ` Kenichi Handa
2003-01-27 10:58 ` Andreas Schwab
2003-01-27 11:09 ` Kenichi Handa
2003-01-27 12:15 ` Andreas Schwab
2003-02-03 0:17 ` Kenichi Handa
2003-02-03 1:24 ` Miles Bader
2003-02-03 2:11 ` Kenichi Handa
2003-02-03 2:22 ` Miles Bader
2003-02-03 8:40 ` Kenichi Handa
2003-02-03 9:02 ` Miles Bader
2003-02-03 9:10 ` Kenichi Handa
2003-02-03 9:22 ` Miles Bader
2003-02-03 9:37 ` Jim Meyering
2003-02-03 11:00 ` Andreas Schwab
2003-02-03 11:17 ` Kenichi Handa
2003-02-13 13:58 ` Dave Love
2003-02-17 6:19 ` Kenichi Handa
2003-02-03 17:47 ` Dave Love
2003-02-03 17:44 ` Dave Love
2003-02-03 18:45 ` Michael Livshin
2003-02-03 19:13 ` Eli Zaretskii
2003-02-03 9:37 ` Jim Meyering
2003-02-03 17:20 ` Richard Stallman
2003-02-03 18:53 ` Andreas Schwab
2003-01-27 10:56 ` Andreas Schwab
2003-01-27 13:35 ` Jim Meyering
2003-01-24 5:42 ` Richard Stallman
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=E18Xgiy-0004Op-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).