unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: dired doesn't work properly with a multibyte locale
Date: Sat, 25 Jan 2003 09:49:15 +0900 (JST)	[thread overview]
Message-ID: <200301250049.JAA11674@etlken.m17n.org> (raw)
In-Reply-To: <buoel74pf7k.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 23 Jan 2003 15:12:15 +0900)

In article <buoel74pf7k.fsf@mcspd15.ucom.lsi.nec.co.jp>, Miles Bader <miles@lsi.nec.co.jp> writes:
> Kenichi Handa <handa@m17n.org> writes:
>>  > This patch seems to work well for me (it correctly parses directories
>>  > that are completely screwed up by the old code).
>> 
>>  Thank you for testing it.  I've just installed that patch in
>>  HEAD.

> I did find one case where things still don't seem to work properly:

> If there's a file containing a newline, then if LANG=C, dired can
> correctly deal with it (e.g., I can put the cursor on it and hit RET,
> and it visits that file), but if LANG=ja_JP.eucjp, then it correctly
> displays all _other_ files, but you can't use RET to visit the
> newline-in-the-file-name file (it says `File no longer exists; type `g'
> to update Dired buffer').

> Since other files work OK in that case, the offsets must be correct, but
> perhaps the chunk-decoding screws up the newline somehow?  Does there
> need to be some sort of fiddling with eol-type?

I've just installed ja_JP.eucJP locale on by debian machine,
and made a file "abc\ndef".  But, it works well in my case
even in ja_JP.eucJP locale.  I tried also a file that
contains Japanese characters and a new line, but still it
works.

So, I have no idea what's wrong with the current code.
Could you debug it?

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2003-01-25  0:49 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
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 [this message]
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=200301250049.JAA11674@etlken.m17n.org \
    --to=handa@m17n.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).