Re: guile can't find a chinese named file

Chris Vine : > On Tue, 14 Feb 2017 21:52:01 + (UTC) > Mike Gran wrote: >> True. Linux should follow OpenBSD and make all locales UTF-8. > > Filenames and locales are not necessarily related. Linux *could* force that reality. > When you access

Re: guile can't find a chinese named file

Linas Vepstas skribis: > On Mon, Jan 30, 2017 at 1:27 PM, David Kastrup wrote: >> Marko Rauhamaa writes: >>> David Kastrup : Marko Rauhamaa writes: > Guile's mistake was to move to Unicode strings

Re: How to make GNU Guile more successful

David Kastrup writes: > Arne Babenhauserheide writes: > >> Marko Rauhamaa writes: >>> I have typed this message in emacs. >> >> Same for me, but getting people to use Emacs is harder. It might not >> *be* that complicated, but it *feels*

Re: How to make GNU Guile more successful

Marko Rauhamaa writes: > Arne Babenhauserheide : > >> Marko Rauhamaa writes: >>> Then, there's GOOPS, which in my opinion is simply an unnatural way >>> to go about object-oriented programming. It does violence both to >>> ordinary OO way of

Re: guile can't find a chinese named file

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 > > > strings in Linux. > > True. Linux should follow OpenBSD and make all locales UTF-8. Filenames and locales are not

Stack traces

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 problem might hide. > While I've read

Re: guile can't find a chinese named file

Mike Gran : > On Tuesday, February 14, 2017 1:07 PM, Marko Rauhamaa > wrote: >> Unicode strings are a special data type that have relatively little> >> practical use. Byte strings are much more fundamental. C's "char *" >> is perfect. > > Human language itself

Re: guile-user Digest, Vol 171, Issue 14

Le 14/02/2017 à 18:24, Cecil McGregor a écrit : As a relative noobie to Guile I have some grievances with Guile. I started to use it for awhile, get frustrated and go away, and then, eventually, come back. My first problem lies in the lack of a decent debugger. (I can hear the screams of more

Re: How to make GNU Guile more successful

Panicz Maciej Godek writes: > There's surely many ways to approach that issue. The point is that for > some reason, Schemers from various tribes prefer to reinvent the > wheel, rather than use an existing one. (Not that I am any different) > However, I also think that

Re: guile can't find a chinese named file

Mike Gran : > The great difficulty with the UTF-8 Guile prototype was the need to > interrogate every string access or index to decide if it was a > codepoint index or a byte index. Unicode strings are a special data type that have relatively little practical use. Byte strings

Re: How to make GNU Guile more successful

Linas Vepstas : > Unicode is just a bunch of bytes that are null-terminated. That is not what Unicode is. Maybe you are thinking of UTF-8, an ingenious way to map a Unicode sequence onto a byte sequence. Trouble is, there are byte sequences that are illegal UTF-8. While

Re: guile can't find a chinese named file

On Mon, Jan 30, 2017 at 1:27 PM, David Kastrup wrote: > Marko Rauhamaa writes: >> David Kastrup : >>> Marko Rauhamaa writes: Guile's mistake was to move to Unicode strings in the operating system interface. >>> >>> Emacs

Re: How to make GNU Guile more successful

Hey, On Mon, Feb 13, 2017 at 11:59 PM, Marko Rauhamaa wrote: > > Arne Babenhauserheide : > > > Marko Rauhamaa writes: > >> Then, there's GOOPS, which in my opinion is simply an unnatural way > >> to go about object-oriented programming. It

Re: guile-user Digest, Vol 171, Issue 14

Cecil McGregor writes: > 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 problem > might hide. While I've read advice to allow the appearance of >

Re: Help formatting a UTC Timestamp

On Tue, 14 Feb 2017 12:27:16 + Guy Baumann wrote: > I am trying to format a timestamp from an api. It is sent in the > format "2011-03-24T20:30:47Z" > > what I want to output is something like this > (strftime "%d %b %g " (localtime (current-time)) ) > > However I am

Re: Help formatting a UTC Timestamp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Feb 14, 2017 at 12:27:16PM +, Guy Baumann wrote: > I am trying to format a timestamp from an api. It is sent in the > format "2011-03-24T20:30:47Z" > > what I want to output is something like this > (strftime "%d %b %g " (localtime

Help formatting a UTC Timestamp

I am trying to format a timestamp from an api. It is sent in the format "2011-03-24T20:30:47Z" what I want to output is something like this (strftime "%d %b %g " (localtime (current-time)) ) However I am unable to work out how to do this, have tried using string->date with results below Enter

Re: How to make GNU Guile more successful

2017-02-13 23:54 GMT+01:00 Arne Babenhauserheide : > > Panicz Maciej Godek writes: > > > 2017-02-13 12:06 GMT+01:00 Arne Babenhauserheide : > > There's also this problem with Scheme that it is a very diverse > > community with plethora of