[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs misbehaves without --unibyte
|
From: |
Paul Stoeber |
|
Subject: |
Re: emacs misbehaves without --unibyte |
|
Date: |
Wed, 29 May 2002 02:18:18 +0200 |
|
User-agent: |
Mutt/1.3.28i |
On Wed, May 29, 2002 at 12:40:42AM +0300, Eli Zaretskii wrote:
> > From: Paul Stoeber <paul.stoeber@stud.tu-ilmenau.de>
> > Date: Tue, 28 May 2002 22:08:14 +0200
> >
> > Neither (setq set-language-environment "Latin-1") nor
> > (setq file-name-coding-system 'latin-1) creates an 8-bit clean
> > environment.
>
> Emacs is a text editor, not a binary file editor. So 8-bit cleanness
> is not the most important goal for it.
>
> There are specialized modes, such as hexl, for editing binary files.
(How is Emacs not a binary file editor when it has hexl mode?)
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). Is it reasonable
for Emacs to refuse to open existing files and to invent new file names
in place of existing ones?