unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: nalaginrut <nalaginrut@gmail.com>
Cc: 13008@debbugs.gnu.org
Subject: bug#13008: Invalid oct number convertion in string
Date: Wed, 28 Nov 2012 14:41:42 +0100	[thread overview]
Message-ID: <877gp5deuh.fsf@gnu.org> (raw)
In-Reply-To: <1354069924.11146.29.camel@Renee-desktop.suse> (nalaginrut@gmail.com's message of "Wed, 28 Nov 2012 10:32:04 +0800")

nalaginrut <nalaginrut@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’.





      parent reply	other threads:[~2012-11-28 13:41 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
2012-11-28 13:41     ` Ludovic Courtès [this message]

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=877gp5deuh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=13008@debbugs.gnu.org \
    --cc=nalaginrut@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).