Re: guile can't find a chinese named file

Eli Zaretskii : > Btw, if by "UCS-2" you meant to say that only characters within the > BMP are supported in file names on Windows, then this is wrong No, I'm claiming Windows allows pathnames to contain isolated surrogate code points, which cannot be decoded back to Unicode with

Re: guile can't find a chinese named file

Eli Zaretskii : >> From: Marko Rauhamaa >> Cc: to...@tuxteam.de, guile-user@gnu.org >> Date: Thu, 16 Feb 2017 08:15:57 +0200 >> >> It is possible to have illegal Unicode even in Windows filenames, ie, >> filenames not expressible using Guile's strings. > > Is it

Re: guile can't find a chinese named file

> Date: Thu, 16 Feb 2017 08:29:14 +0200 > From: Eli Zaretskii > Cc: guile-user@gnu.org > > > From: Marko Rauhamaa > > Cc: to...@tuxteam.de, guile-user@gnu.org > > Date: Thu, 16 Feb 2017 08:15:57 +0200 > > > > It is possible to have illegal Unicode even in

Re: guile can't find a chinese named file

> From: Marko Rauhamaa > Cc: to...@tuxteam.de, guile-user@gnu.org > Date: Thu, 16 Feb 2017 08:15:57 +0200 > > It is possible to have illegal Unicode even in Windows filenames, ie, > filenames not expressible using Guile's strings. Is it really possible? Can you show a code

Re: guile can't find a chinese named file

Eli Zaretskii : >> From: Marko Rauhamaa >> Cc: to...@tuxteam.de, guile-user@gnu.org >> Date: Wed, 15 Feb 2017 23:04:52 +0200 >> >> Eli Zaretskii : >> >> > At the file system level (for NTFS volumes at least) Windows file >> > names are always

Re: guile can't find a chinese named file

> Date: Wed, 15 Feb 2017 22:15:52 +0100 > From: to...@tuxteam.de > Cc: guile-user@gnu.org > > > > > A possible solution would be to decode each mount point's part as it > > > > is being resolved. > > > > > > ...which can only be based on guesswork: there's no reliable info on > > > the encoding

Re: guile can't find a chinese named file

> From: Marko Rauhamaa > Cc: to...@tuxteam.de, guile-user@gnu.org > Date: Wed, 15 Feb 2017 23:04:52 +0200 > > Eli Zaretskii : > > > At the file system level (for NTFS volumes at least) Windows file > > names are always UTF-16 encoded, and Windows just "knows"

Re: Stack traces

> On Feb 15, 2017, at 7:36 AM, Christopher Allan Webber > wrote: > > One thing that we see requested a lot is how to do the equivalent of: > > import pdb > pdb.set_trace() > > in python, just dumping something to "trigger" the debugger somewhere. > I seem to

Re: guile can't find a chinese named file

Eli Zaretskii : > At the file system level (for NTFS volumes at least) Windows file > names are always UTF-16 encoded, and Windows just "knows" that. Hm, I had the impression NTFS filenames were UCS-2 (https://en.wikipedia.org/wiki/Talk%3AUTF-16/UCS-2>). Marko

Re: guile can't find a chinese named file

> Date: Wed, 15 Feb 2017 21:20:56 +0100 > From: to...@tuxteam.de > Cc: guile-user@gnu.org > > > > Most notably, the whole path might cross several mount points, thus > > > the whole path can well have fragments coming from several file systems. > > > > A possible solution would be to decode each

Re: guile can't find a chinese named file

> Date: Wed, 15 Feb 2017 21:07:53 +0100 > From: to...@tuxteam.de > Cc: to...@tuxteam.de, d...@gnu.org, guile-user@gnu.org > > > It took many years because those smart, experienced, and patient > > people made bad decisions, twice, and had to correct them later, which > > required rewriting

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 06:59:14PM +0200, Eli Zaretskii wrote: > > Date: Wed, 15 Feb 2017 10:18:32 +0100 > > From: [...] > > Most notably, the whole path might cross several mount points, thus > > the whole path can well have

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 07:04:10PM +0200, Eli Zaretskii wrote: > > Date: Wed, 15 Feb 2017 11:10:33 +0100 > > From: > > Cc: guile-user@gnu.org > > > > Yes, Emacs is the text specialist. > > > > It has taken years and a bunch of

Re: guile can't find a chinese named file

Eli Zaretskii : >> Date: Wed, 15 Feb 2017 10:18:32 +0100 >> From: >> I think the only sane way to see a Linux file system path is the way >> Linux sees it: as a byte string. > > This would lose a lot in 99% of use cases. You are, in effect, > suggesting a "reverse

Re: guile can't find a chinese named file

> Date: Wed, 15 Feb 2017 10:18:32 +0100 > From: > > > Filenames and locales are not necessarily related. When you access a > > networked file system, you get the filename encoding you are given, > > which may or may not be the same as the particular locale encoding on > > your

Re: Stack traces

Ludovic Courtès writes: > Hello, > > Cecil McGregor skribis: > >> My first problem lies in the lack of a decent debugger. >> (I can hear the screams of more enlightened Guilers >> already!) The stack traces seldom provide filenames >> and line numbers to hint where a

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 01:11:57PM +, Chris Vine wrote: > On Wed, 15 Feb 2017 13:41:24 +0100 > wrote: > [snip] > > What I don't like about the fluid is that it still doesn't give you > > an escape hatch in hard cases (your USB

Re: guile can't find a chinese named file

On Wed, 15 Feb 2017 13:41:24 +0100 wrote: [snip] > What I don't like about the fluid is that it still doesn't give you > an escape hatch in hard cases (your USB stick example). The program would just have to document that any mount point must have a path in a character set (eg

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 12:13:09PM +, Chris Vine wrote: > On Wed, 15 Feb 2017 12:48:20 +0100 > wrote: > > On Wed, Feb 15, 2017 at 10:15:33AM +, Chris Vine wrote: > [snip] > > > I would prefer guile to make the filename

Re: guile can't find a chinese named file

: > On Wed, Feb 15, 2017 at 12:58:41AM +0100, David Kastrup wrote: >> LilyPond is getting removed from Debian and other distributions >> because it is still hopeless to get it to run under Guile-2 (the >> experimental support has encoding and stability problems and runs >> about

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 10:15:33AM +, Chris Vine wrote: [...] > I don't disagree. My purpose was to point out that in the modern > world of networking and plug-in devices, locales and filenames are > disjoint. > > The glib approach is better

Re: guile can't find a chinese named file

Marko Rauhamaa writes: > David Kastrup : > >> If you tell Emacs that some external entity is in UTF-8, it will >> represent all valid UTF-8 sequences as properly decoded characters, >> and it has special codes for all bytes not part of valid UTF-8. >> >> As a

Re: guile can't find a chinese named file

David Kastrup : > If you tell Emacs that some external entity is in UTF-8, it will > represent all valid UTF-8 sequences as properly decoded characters, > and it has special codes for all bytes not part of valid UTF-8. > > As a result, it works with valid UTF-8 perfectly as expected

Re: guile can't find a chinese named file

On Wed, 15 Feb 2017 10:18:32 +0100 wrote: > On Tue, Feb 14, 2017 at 10:19:14PM +, Chris Vine wrote: [snip] > > Filenames and locales are not necessarily related. When you access > > a networked file system, you get the filename encoding you are > > given, which may or may

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 12:58:41AM +0100, David Kastrup wrote: [...] > Not just on yours. LilyPond is probably the largest application using > Guile as its extension language, with pretty much the worst impacts of > Guile-2 design decisions. So

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 15, 2017 at 10:54:06AM +0100, David Kastrup wrote: > writes: [...] > > Not easy. > > If you tell Emacs that some external entity is in UTF-8, it will > represent all valid UTF-8 sequences as properly decoded

Re: guile can't find a chinese named file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Feb 14, 2017 at 10:19:14PM +, Chris Vine wrote: > On Tue, 14 Feb 2017 21:52:01 + (UTC) > Mike Gran wrote: > [snip] > > > In particular, filenames are *not*, nor can they be mapped to, > > > Unicode > > > > >