Reported as bug #9:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=9
2015-12-22 12:56 GMT-03:00 Marko Rauhamaa :
> Vicente Vera :
>
>> Should this be sent to the bugs list?
>
> Go ahead.
>
>
> Marko
Marko Rauhamaa skribis:
> I'm a bit sorry that Guile repeated Python 3's mistake and brought
> (Unicode) strings to the center. Strings are a highly special-purpose
> data structure; I really never had a real need for them in my decades of
> programming. Also, I suspect strings are much too simpli
Marko Rauhamaa writes:
> David Kastrup :
>
>> That's more economical than Python's method which uses the encodings
>> of surrogate words not allowed in properly encoded UTF-8, taking
>> 3 bytes rather than the 2 Emacs makes do with. Using high codepoints
>> above the Unicode space would even take
David Kastrup :
> That's more economical than Python's method which uses the encodings
> of surrogate words not allowed in properly encoded UTF-8, taking
> 3 bytes rather than the 2 Emacs makes do with. Using high codepoints
> above the Unicode space would even take 4 bytes.
Actually, CPython rep
Eli Zaretskii writes:
> From: Marko Rauhamaa
>
>> Why don't you tell me already what emacs does?
>
> I did, you elided that. It represents text as superset of UTF-8, and
> uses high codepoints above the Unicode space for raw bytes.
Incorrect. It uses overlong encodings of 0x00-0x7f for raw by
Eli Zaretskii :
>> From: Marko Rauhamaa
>> Why don't you tell me already what emacs does?
>
> I did, you elided that. It represents text as superset of UTF-8, and
> uses high codepoints above the Unicode space for raw bytes.
Excellent. If that works, Guile needs the same thing.
(I'm afraid, tho
> From: Marko Rauhamaa
> Cc: guile-user@gnu.org
> Date: Wed, 23 Dec 2015 21:18:28 +0200
>
> Eli Zaretskii :
>
> >> From: Marko Rauhamaa
> >> The Linux kernel just doesn't care, and shouldn't.
> >
> > Guile is not an OS kernel. Guile is an environment for writing
> > applications. On the applica
Eli Zaretskii :
>> From: Marko Rauhamaa
>> The Linux kernel just doesn't care, and shouldn't.
>
> Guile is not an OS kernel. Guile is an environment for writing
> applications. On the application level, you _should_ care, or else you
> won't be able to manipulate file names in meaningful ways.
T
> From: Marko Rauhamaa
> Date: Tue, 22 Dec 2015 23:39:28 +0200
> Cc: guile-user@gnu.org
>
> > No, they aren't, not as file names. E.g., you cannot meaningfully
> > downcase or upcase such "characters", you cannot count characters (as
> > opposed to bytes), you cannot calculate how much screen est
Eli Zaretskii :
>> From: Marko Rauhamaa
>> By setting the character set artificially to Latin-1 in Guile, all
>> pathnames are accessible to it.
>
> No, they aren't, not as file names. E.g., you cannot meaningfully
> downcase or upcase such "characters", you cannot count characters (as
> opposed
> From: Marko Rauhamaa
> Date: Tue, 22 Dec 2015 22:36:07 +0200
> Cc: guile-user@gnu.org
>
> By setting the character set artificially to Latin-1 in Guile, all
> pathnames are accessible to it.
No, they aren't, not as file names. E.g., you cannot meaningfully
downcase or upcase such "characters"
Chris Vine :
> So I guess the best rule is that, even if you don't stick to the
> Portable Filename Character Set, stick to ASCII for filenames/paths.
The filenames are not in my control or Guile's. Guile can't simply wish
the filenames to be strings, or, like Python, it would at least need
some
On Tue, 22 Dec 2015 17:55:58 +0200
Marko Rauhamaa wrote:
> Chris Vine wrote:
> > On Tue, 22 Dec 2015 03:14:18 +0200
> > Marko Rauhamaa wrote:
> >> For example,
> >>
> >> scheme@(guile-user)> (opendir ".")
> >> $1 = #
> >> [...]
> >> scheme@(guile-user)> (readdir $1)
> >> $
Vicente Vera :
> Should this be sent to the bugs list?
Go ahead.
Marko
Chris Vine :
> On Tue, 22 Dec 2015 03:14:18 +0200
> Marko Rauhamaa wrote:
>> For example,
>>
>> scheme@(guile-user)> (opendir ".")
>> $1 = #
>> [...]
>> scheme@(guile-user)> (readdir $1)
>> $4 = "?9t\x1b["
>> scheme@(guile-user)> (open-file $4 "r")
>> ERROR: In proced
Should this be sent to the bugs list?
2015-12-21 20:19 GMT-03:00 Marko Rauhamaa :
> Vicente Vera :
>
>> Hello. I'm sorry if this is the wrong list (I'm not sure if its a
>> bug).
>
> Must be a bug.
>
>> I wrote a small test script:
>
> The error is reproduced with an empty scm file:
>
>touch t
On Tue, 22 Dec 2015 03:14:18 +0200
Marko Rauhamaa wrote:
> Chris Vine :
>
> > I think the problem is that calling the native 'primitive-load'
> > procedure on a filename with UTF-8 encoding with a character outside
> > the ASCII range (when the locale encoding is also UTF-8) fails to
> > work unl
Chris Vine :
> I think the problem is that calling the native 'primitive-load'
> procedure on a filename with UTF-8 encoding with a character outside
> the ASCII range (when the locale encoding is also UTF-8) fails to work
> unless you call '(set-locale LC_ALL "")' in the program first.
>
> Of cou
On Tue, 22 Dec 2015 01:19:36 +0200
Marko Rauhamaa wrote:
> Vicente Vera :
>
> > Hello. I'm sorry if this is the wrong list (I'm not sure if its a
> > bug).
>
> Must be a bug.
>
> > I wrote a small test script:
>
> The error is reproduced with an empty scm file:
>
>touch test.scm
>
Vicente Vera :
> Hello. I'm sorry if this is the wrong list (I'm not sure if its a
> bug).
Must be a bug.
> I wrote a small test script:
The error is reproduced with an empty scm file:
touch test.scm
guile test.scm
[...]
ERROR: In procedure open-file: No such file or directory: [..
Hello. I'm sorry if this is the wrong list (I'm not sure if its a bug).
I wrote a small test script:
#!/usr/bin/guile -s
!#
;; coding: utf-8
(display "hey")
(newline)
This happens when I try to run it from a directory with UTF-8 characters:
$ cd ~/código/
$ ./test.scm
;;; Stat of /home/me/c??di
21 matches
Mail list logo
