unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: nalaginrut <nalaginrut@gmail.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: 13008@debbugs.gnu.org
Subject: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 13:58:51 +0800	[thread overview]
Message-ID: <1354082331.11146.31.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CAN3veRfQ8=4Zy=Bxed6j3hE4i6sb_wj9wjsApS2RZDFvxRV3qA@mail.gmail.com>

On Wed, 2012-11-28 at 11:34 +0800, Daniel Hartwig wrote:
> On 28 November 2012 10:32, nalaginrut <nalaginrut@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?







  reply	other threads:[~2012-11-28  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 10:41 bug#13008: Invalid oct number convertion in string nalaginrut
2012-11-27 22:44 ` Ludovic Courtès
2012-11-28  2:32   ` nalaginrut
2012-11-28  3:34     ` Daniel Hartwig
2012-11-28  5:58       ` nalaginrut [this message]
2012-11-28 13:41     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1354082331.11146.31.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=13008@debbugs.gnu.org \
    --cc=mandyke@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).