GNU bug report logs - #13008
Invalid oct number convertion in string

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13008 in the body.
You can then email your comments to 13008 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: nalaginrut <nalaginrut <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Invalid oct number convertion in string
Date: Tue, 27 Nov 2012 18:41:31 +0800

Here is the story:
=====================cut===============================
scheme@(guile-user)> (format #t "\033[32;31mhello\033[5m")
33[32;31mhello33[5m$2 = #t
scheme@(guile-user)> (format #t "\x1b[32;31mhello\x1b[5m")
hello (in red color)
=====================end===============================

Seems "\033" can't be converted to "\x1b", and I tried "\o1b" failed.
I believe it ought to be a bug.

Message #8 received at 13008 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: nalaginrut <nalaginrut <at> gmail.com>
Cc: 13008 <at> debbugs.gnu.org
Subject: Re: bug#13008: Invalid oct number convertion in string
Date: Tue, 27 Nov 2012 23:44:07 +0100

Hi!

nalaginrut <nalaginrut <at> gmail.com> skribis:

> scheme@(guile-user)> (format #t "\033[32;31mhello\033[5m")

Here, \0 is taken to mean #\nul, and then there are two #\3.

IOW, there is no such syntax for octal escapes (info "(guile) String
Syntax").

What made you think otherwise?

Thanks,
Ludo’.

Message #11 received at 13008 <at> debbugs.gnu.org (full text, mbox):

From: nalaginrut <nalaginrut <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 13008 <at> debbugs.gnu.org
Subject: Re: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 10:32:04 +0800

On Tue, 2012-11-27 at 23:44 +0100, Ludovic Courtès wrote:
> Hi!
> 
> nalaginrut <nalaginrut <at> gmail.com> skribis:
> 
> > scheme@(guile-user)> (format #t "\033[32;31mhello\033[5m")
> 
> Here, \0 is taken to mean #\nul, and then there are two #\3.
> 
> IOW, there is no such syntax for octal escapes (info "(guile) String
> Syntax").
> 
> What made you think otherwise?
> 

Thanks for reply!
It's fine in ruby-1.9 and python2, but python3 failed.
IIRC, Andy told me that guile2/python3 use "character string" rather
than "byte string", so there's different from others.

Now my question is, should we have octal-escapes? Is is impossible or
not implemented yet?

Thanks!

> Thanks,
> Ludo’.

Message #14 received at 13008 <at> debbugs.gnu.org (full text, mbox):

From: Daniel Hartwig <mandyke <at> gmail.com>
To: nalaginrut <nalaginrut <at> gmail.com>
Cc: 13008 <at> debbugs.gnu.org
Subject: Re: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 11:34:25 +0800

On 28 November 2012 10:32, nalaginrut <nalaginrut <at> gmail.com> wrote:
>> > scheme@(guile-user)> (format #t "\033[32;31mhello\033[5m")
>>
>> Here, \0 is taken to mean #\nul, and then there are two #\3.
>>
>> IOW, there is no such syntax for octal escapes (info "(guile) String
>> Syntax").
>>
>> What made you think otherwise?
>>

> Now my question is, should we have octal-escapes? Is is impossible or
> not implemented yet?

You can use two or four digit hex codes, “\xHH” and “\uHHHH”.  Is it
useful to support octal on top of that?

Message #17 received at 13008 <at> debbugs.gnu.org (full text, mbox):

From: nalaginrut <nalaginrut <at> gmail.com>
To: Daniel Hartwig <mandyke <at> gmail.com>
Cc: 13008 <at> debbugs.gnu.org
Subject: Re: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 13:58:51 +0800

On Wed, 2012-11-28 at 11:34 +0800, Daniel Hartwig wrote:
> On 28 November 2012 10:32, nalaginrut <nalaginrut <at> gmail.com> wrote:
> >> > scheme@(guile-user)> (format #t "\033[32;31mhello\033[5m")
> >>
> >> Here, \0 is taken to mean #\nul, and then there are two #\3.
> >>
> >> IOW, there is no such syntax for octal escapes (info "(guile) String
> >> Syntax").
> >>
> >> What made you think otherwise?
> >>
> 
> > Now my question is, should we have octal-escapes? Is is impossible or
> > not implemented yet?
> 
> You can use two or four digit hex codes, “\xHH” and “\uHHHH”.  Is it
> useful to support octal on top of that?

Yes, I can use hex instead. 
But, why we couldn't provide octal? Or it needs to be done?

Message #20 received at 13008 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: nalaginrut <nalaginrut <at> gmail.com>
Cc: 13008 <at> debbugs.gnu.org
Subject: Re: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 14:41:42 +0100

nalaginrut <nalaginrut <at> gmail.com> skribis:

> Now my question is, should we have octal-escapes? Is is impossible or
> not implemented yet?

Nothing’s impossible, but there are already several kinds of escapes,
most of which are standardized, so I don’t think we need another one.

Closing this as not-a-bug.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.