nmh-workers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [nmh-workers] Formatting HTML to Text: netrik.


From: Robert Elz
Subject: Re: [nmh-workers] Formatting HTML to Text: netrik.
Date: Mon, 08 Jul 2019 06:11:50 +0700

    Date:        Sun, 07 Jul 2019 12:56:13 -0700
    From:        "Ronald F. Guilmette" <address@hidden>
    Message-ID:  <address@hidden>

  | But to answer Ralph's inquiry...
  |
  |
  | LANG=en_US.UTF-8
  | LC_CTYPE="en_US.UTF-8"
  | LC_COLLATE="en_US.UTF-8"
  | LC_TIME="en_US.UTF-8"
  | LC_NUMERIC="en_US.UTF-8"
  | LC_MONETARY="en_US.UTF-8"
  | LC_MESSAGES="en_US.UTF-8"
  | LC_ALL=

That looks wrong ... that last line undoes the effect of all of the
others, when LC_ALL is set, it overridses everything else.  (Though
XTERM_LOCALE isn't one of this set and is entirely unrelated).
Nb: it is not the order that matters, it is having LC_ALL set at all.

In general, LC_ALL should almost never be set except in a usage like

        LC_ALL=C grep ...

in a script, where you want (need) to return temporarily to the default
locale in order to run one particular command that way (so any other
locale settings that may be in the environment are temporarily ignored).
(This can be needed to make things like '[a-z]' work properly in the pattern.)

You *never* want it set in the environment.

Setting LANG along with all the others is also kind of useless, but that
one is harmless - that's the fallback default for the LC_xxx's that aren't
set.

The double quotes that are used are also not needed - but those affect
nothing and are largely an issue of style.

kre




reply via email to

[Prev in Thread] Current Thread [Next in Thread]