bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error bunzip2ing files with non-ASCI-names


From: Kevin Rodgers
Subject: Re: Error bunzip2ing files with non-ASCI-names
Date: Tue, 24 Jan 2006 09:46:26 -0700
User-agent: Mozilla Thunderbird 0.9 (X11/20041105)

Rommerskirchen, Heinrich wrote:
In GNU Emacs 21.3.1 (i586-suse-linux, X toolkit, Xaw3d scroll bars)
 of 2005-03-22 on lorien
configured using `configure '--with-gcc' '--with-pop' '--with-leim' 
'--with-system-malloc' '--prefix=/usr' '--infodir=/usr/share/info' 
'--mandir=/usr/share/man' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' 
'--with-x' '--with-xpm' '--with-jpeg' '--with-tiff' '--with-gif' '--with-png' 
'--with-x-toolkit=lucid' '--x-includes=/usr/X11R6/include' 
'--x-libraries=/usr/X11R6/lib' 'i586-suse-linux' 'CC=gcc' 'CFLAGS=-O2 
-march=i586 -mcpu=i686 -fmessage-length=0 -Wall -g -pipe -fno-strict-aliasing   
     -DSYSTEM_PURESIZE_EXTRA=25000   -DSITELOAD_PURESIZE_EXTRA=10000         
-D_GNU_SOURCE ' 'LDFLAGS=-s' 'build_alias=i586-suse-linux' 
'host_alias=i586-suse-linux' 'target_alias=i586-suse-linux''
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: de_DE.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

On my GNU/Linux (SuSE 9.3) workstation emacs is unable to bunzip2
files whose names are not ASCII, maybe because file names are utf-8 encoded on
this system.

Steps to reproduce this bug:
In the shell:
  > echo xx > bä.txt     # the second letter of the filename is a-Umlaut
> bzip2 bä.txt > emacs -q --no-site-file
In emacs
- type "M-x auto-compression-mode"
- open a dired buffer which contains the file (the filename is displayed
correctly with the Umlaut), - move point to the file and press enter The error message "File exists, but cannot be read" is displayed and an empty buffer is created. If I rename the file with dired-do-rename to
'bae.txt.bz2', the file can be opened without any problems.
bunzip2 has no problems to unzip the file with its original name (tests started
from eshell, xterm, text-only terminal)
The same happens if I use gzip instead of bzip2.

Files which are not compressed can be read without problems, even if their names
contain non-ASCII characters. Uncompressing the file 'bä.txt.bz2' in a dired
buffer with 'Z' (dired-do-compress) works, too, and gives the readable file
'bä.txt'.

What happens if you visit bä.txt with `C-x C-f' instead of via Dired?

--
Kevin Rodgers





reply via email to

[Prev in Thread] Current Thread [Next in Thread]