zsh-workers
 help / color / mirror / code / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] avoid localized output from external commands in a few completion
Date: Tue, 26 Dec 2017 13:47:01 +0900	[thread overview]
Message-ID: <19CB3093-E02F-48F1-AE9D-8A446FED7540@kba.biglobe.ne.jp> (raw)
In-Reply-To: <1514251193.2800192.1215805184.324D9E4C@webmail.messagingengine.com>


> 2017/12/26 10:19、Daniel Shahaf <d.s@daniel.shahaf.name>のメール:
> 
> Bart Schaefer wrote on Mon, 25 Dec 2017 17:04 -0800:
>> On Mon, Dec 25, 2017 at 3:40 PM, Jun T. <takimoto-j@kba.biglobe.ne.jp> wrote:
>>> In some recent Linux distributions, output from commands
>>> like 'nm --help' is localized and can't be analyzed correctly
>>> by completion scripts. We need to reset LC_MESSAGES.
>> 
> 
> That won't help if LC_ALL is set.  Shouldn't we just set LC_ALL=C, or
> use _comp_locale?

Oops, sorry. We need to reset LC_ALL.
I didn't know _comp_locale; is it documented somewhere?

>> Perhaps this is something that would better be done by _main_complete?

Might be, but I'm not sure.

zsh% tar --<TAB>

gives a list of long options with localized description, because the output
of 'tar --help' is localized and _tar uses '_arguments --' for completing
long options. Although the localized description may not be "perfect", some
user would still want to see it.

How about adding an option (say -l) to _call_program so that _comp_locale
is called before the command?

  reply	other threads:[~2017-12-26  4:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25 23:40 Jun T.
2017-12-26  1:04 ` Bart Schaefer
2017-12-26  1:19   ` Daniel Shahaf
2017-12-26  4:47     ` Jun T [this message]
2017-12-26  4:59       ` Jun T
2017-12-26 10:52         ` Jun T
2017-12-27 11:51           ` Jun T
2017-12-27 23:15             ` Daniel Shahaf
2017-12-28  2:54               ` Jun T
2017-12-26  5:24       ` Daniel Shahaf

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

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

  git send-email \
    --in-reply-to=19CB3093-E02F-48F1-AE9D-8A446FED7540@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).