From: Andy Wingo <wingo@pobox.com>
To: Zefram <zefram@fysh.org>
Cc: 22905@debbugs.gnu.org
Subject: bug#22905: GUILE_INSTALL_LOCALE produces unavoidable noise
Date: Sun, 07 Aug 2016 23:58:11 +0200 [thread overview]
Message-ID: <878tw8nswc.fsf@pobox.com> (raw)
In-Reply-To: <20160304141334.GC7946@fysh.org> (zefram@fysh.org's message of "Fri, 4 Mar 2016 14:13:34 +0000")
On Fri 04 Mar 2016 15:13, Zefram <zefram@fysh.org> writes:
> GUILE_INSTALL_LOCALE=1 breaks some of the robustness of non-locale-using
> programs, marring their stderr output if the environment's locale settings
> are faulty.
I believe this is consistent with other programs which call setlocale,
notably Perl and Bash. I think the right way to avoid the output is to
avoid the call to setlocale, and Guile offers the GUILE_INSTALL_LOCALE=0
knob to do this.
> However, if it is deemed to be essential that Guile attempt the implicit
> setlocale and gripe about its failure, then the message should not
> precede or otherwise mix with the actual program run. The message should
> be emitted *instead of* running the program, declaring the absolute
> incompatibility of the Guile framework with this environmental condition.
Your suggestion is not what Perl or Bash does, FWIW. But it is
possible -- we could emit an error and require the user to run with
GUILE_INSTALL_LOCALE=0. Or we could add that suggestion to the
warning. Probably adding the suggestion to the warning is the right
thing; wdyt? Try "LC_ALL=fasdada perl" for an example.
Andy
next prev parent reply other threads:[~2016-08-07 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:13 bug#22905: GUILE_INSTALL_LOCALE produces unavoidable noise Zefram
2016-08-07 21:58 ` Andy Wingo [this message]
2016-08-07 23:00 ` Zefram
2016-08-08 20:17 ` Andy Wingo
2016-08-08 21:02 ` Zefram
2016-08-09 17:39 ` Andy Wingo
2016-08-09 19:26 ` Zefram
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=878tw8nswc.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=22905@debbugs.gnu.org \
--cc=zefram@fysh.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).