[debbugs-tracker] bug#4151: closed (non-utf locale leads to errors in `decode-coding-region' (dired))

[GNU bug Tracking System]

Your message dated Thu, 11 Feb 2016 15:55:47 -0500
with message-id <address@hidden>
and subject line Re: bug#4151: non-utf locale leads to errors in 
`decode-coding-region' (dired)
has caused the debbugs.gnu.org bug report #4151,
regarding non-utf locale leads to errors in `decode-coding-region' (dired)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
4151: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=4151
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> non-utf locale leads to errors in `decode-coding-region' (dired)
>
>
>
>
> Date: 
>
> Sat, 15 Aug 2009 08:10:32 -0400
>
>
>
>
> With
>
> export LANG=de_DE.ISO8859-15
>
> on a Mac (NS port), and a directory that contains a folder named  
> "Tätää"(i.e. a German umlaut), viewing the directory with `dired'  
> fails with an error message.  The trace is below.
>
> The bugs here are
> 1. `decode-coding-region' signals an error (it is not documented to do  
> so)
> 2. with this locale, "ls -la" will not output utf-8-nfd, even though  
> it seems that we expect this.
>
>
>
>
> Debugger entered--Lisp error: (wrong-type-argument wholenump nil)
>   decode-coding-region(1 8177 utf-8-nfd)
>   insert-directory("/Users/dr/" "-al" nil t)
>   dired-insert-directory("/Users/dr/" "-al" nil nil t)
>   dired-readin-insert()
>   dired-readin()
>   dired-internal-noselect("~/" nil)
>   dired-noselect("~/")
>   run-hook-with-args-until-success(dired-noselect "~/")
>   find-file-noselect("~/" nil nil t)
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#4151: non-utf locale leads to errors in `decode-coding-region' (dired)
>
>
>
>
> Date: 
>
> Thu, 11 Feb 2016 15:55:47 -0500
>
>
>
>
> On Feb 11, 2016, at 3:45 PM, Alan Third <address@hidden> wrote:
> > 
> > Hi, I can't reproduce this with Emacs 25. Are you still seeing this
> > problem with a recent build?
>
> I do not.  It seems to have been fixed.
>
> Thanks for checking on it.  Closing the bug.
>
>
>
>
> --- End Message ---