[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs misbehaves without --unibyte
From: |
Eli Zaretskii |
Subject: |
Re: emacs misbehaves without --unibyte |
Date: |
Wed, 29 May 2002 12:00:50 +0300 (IDT) |
On Wed, 29 May 2002, Paul Stoeber wrote:
> On Wed, May 29, 2002 at 09:23:11AM +0300, Eli Zaretskii wrote:
> > > I started this thread because default emacs wouldn't let me navigate
> > > filesystems that contain funny filenames, so the "8-bit cleanness"
> > > discussion only applies to file name handling (although I had also
> > > mentioned "text/binary files" in a general statement).
> >
> > For that, Miles gave the solution: you should set up your language
> > environment correctly, or set file-name-coding-system explicitly.
>
> Yes. If you simply want to use dired as a robust filesystem browser
> (like bash, only more comfortable), regardless of your language
> or the language of who created the files, then
>
> (setq file-name-coding-system 'no-conversion)
>
> seems to be a solution.
Should we perhaps make no-conversion be the default value of
file-name-coding-system, instead of nil?
- Re: emacs misbehaves without --unibyte,
Eli Zaretskii <=
Re: emacs misbehaves without --unibyte, Richard Stallman, 2002/05/30