unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, guile-devel@gnu.org
Subject: Re: Accessing the environment's locale encoding settings
Date: Thu, 15 Dec 2011 01:41:32 +0100	[thread overview]
Message-ID: <87k45y8y4j.fsf@gnu.org> (raw)
In-Reply-To: <201111202112.46974.bruno@clisp.org> (Bruno Haible's message of "Sun, 20 Nov 2011 21:12:46 +0100")

Hi,

Since adding an implicit setlocale(LC_ALL, "") cannot be done in Guile
2.0 (it would change the default port encoding as a side effect, etc.),
I committed something similar to the hack proposed in [0].

Bruno Haible <bruno@clisp.org> skribis:

> If I were you, I would start using the gnulib-tool option --local-dir
> with a local modification of the 'localcharset' module, as documented in [1].

I followed your suggestion:

  http://git.sv.gnu.org/cgit/guile.git/tree/gnulib-local/lib?h=stable-2.0

Thanks!

Ludo’.

[0] http://lists.gnu.org/archive/html/guile-devel/2011-11/msg00039.html



      reply	other threads:[~2011-12-15  0:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  0:13 Accessing the environment's locale encoding settings Ludovic Courtès
2011-11-16  2:00 ` Bruno Haible
2011-11-16 10:35   ` Ludovic Courtès
2011-11-16 16:11     ` Noah Lavine
2011-11-16 16:32       ` Peter Brett
2011-11-18 22:17         ` Mark H Weaver
2011-11-20 16:55     ` Bruno Haible
2011-11-20 17:41       ` Ludovic Courtès
2011-11-20 19:44         ` Mike Gran
2011-11-23 23:28           ` Ludovic Courtès
2011-11-24  4:42             ` Mike Gran
2011-11-24 13:16             ` Peter Brett
2011-11-25  2:11             ` Mark H Weaver
2011-12-15 19:08               ` Ludovic Courtès
2011-11-20 20:12         ` Bruno Haible
2011-12-15  0: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=87k45y8y4j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).