all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Error bunzip2ing files with non-ASCI-names
@ 2006-01-23 14:13 Rommerskirchen, Heinrich
  2006-01-24 16:46 ` Kevin Rodgers
       [not found] ` <mailman.2371.1138121825.26925.bug-gnu-emacs@gnu.org>
  0 siblings, 2 replies; 4+ messages in thread
From: Rommerskirchen, Heinrich @ 2006-01-23 14:13 UTC (permalink / raw)



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'.


Recent input:
<help-echo> <help-echo> M-x a u t o - c o m <tab> <return> 
C-x d <return> <down> <down> <down> <return> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <menu-bar> 
<help-menu> <report-emacs-bug>

Recent messages:
Loading tooltip...done
For information about the GNU Project and its goals, type C-h C-p.
Loading image...done
Loading jka-compr...done
Auto-Compression mode enabled
Loading dired...done
Reading directory /home/hz/tmp/...done
bunzip2ing bä.txt.bz2...done
File exists, but cannot be read
Loading emacsbug...done

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Error bunzip2ing files with non-ASCI-names
  2006-01-23 14:13 Error bunzip2ing files with non-ASCI-names Rommerskirchen, Heinrich
@ 2006-01-24 16:46 ` Kevin Rodgers
       [not found] ` <mailman.2371.1138121825.26925.bug-gnu-emacs@gnu.org>
  1 sibling, 0 replies; 4+ messages in thread
From: Kevin Rodgers @ 2006-01-24 16:46 UTC (permalink / raw)


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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Error bunzip2ing files with non-ASCI-names
       [not found] ` <mailman.2371.1138121825.26925.bug-gnu-emacs@gnu.org>
@ 2006-01-26  8:05   ` Heinz Rommerskirchen
  2006-01-26 21:58     ` Kevin Rodgers
  0 siblings, 1 reply; 4+ messages in thread
From: Heinz Rommerskirchen @ 2006-01-26  8:05 UTC (permalink / raw)


Kevin Rodgers <ihs_4664@yahoo.com> writes:

> Rommerskirchen, Heinrich wrote:
snip
>> 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
snip
>
> What happens if you visit bä.txt with `C-x C-f' instead of via Dired?
>
> -- 
> Kevin Rodgers

I assumed you mean open bä.txt.bz2 with `C-x C-f'; this gives the same
behaviour (error message and empty buffer). bä.txt can be opened in any
way I can think of without problems

-- 
Regards

Heinz

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Error bunzip2ing files with non-ASCI-names
  2006-01-26  8:05   ` Heinz Rommerskirchen
@ 2006-01-26 21:58     ` Kevin Rodgers
  0 siblings, 0 replies; 4+ messages in thread
From: Kevin Rodgers @ 2006-01-26 21:58 UTC (permalink / raw)


Heinz Rommerskirchen wrote:
 > Kevin Rodgers <ihs_4664@yahoo.com> writes:
 >>What happens if you visit bä.txt with `C-x C-f' instead of via Dired?
 >
 > I assumed you mean open bä.txt.bz2 with `C-x C-f'; this gives the same
 > behaviour (error message and empty buffer). bä.txt can be opened in any
 > way I can think of without problems

Sorry, that is what I meant.  This problem was just fixed today in CVS
(Emacs 22): 
http://lists.gnu.org/archive/html/emacs-devel/2006-01/msg00958.html

-- 
Kevin Rodgers

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-01-26 21:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-23 14:13 Error bunzip2ing files with non-ASCI-names Rommerskirchen, Heinrich
2006-01-24 16:46 ` Kevin Rodgers
     [not found] ` <mailman.2371.1138121825.26925.bug-gnu-emacs@gnu.org>
2006-01-26  8:05   ` Heinz Rommerskirchen
2006-01-26 21:58     ` Kevin Rodgers

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.