Zsh Mailing List Archive
Messages sorted by:
Re: problems with 4.3.4 and Tru64
- X-seq: zsh-workers 23423
- From: Timo Aaltonen <tjaalton@xxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: problems with 4.3.4 and Tru64
- Date: Thu, 10 May 2007 16:05:42 +0300 (EEST)
- In-reply-to: <20070510125556.c4df10c1.pws@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <Pine.OSF.4.64.0705101117330.479844@xxxxxxxxxxxxxxxx> <200705100955.l4A9tTmQ001343@xxxxxxxxxxxxxx> <Pine.OSF.4.64.0705101305200.479844@xxxxxxxxxxxxxxxx> <Pine.OSF.4.64.0705101310130.479844@xxxxxxxxxxxxxxxx> <20070510113032.3d50cd67.pws@xxxxxxx> <Pine.OSF.4.64.0705101334180.479844@xxxxxxxxxxxxxxxx> <20070510123039.c36e16f2.pws@xxxxxxx> <Pine.OSF.4.64.0705101438080.479844@xxxxxxxxxxxxxxxx> <20070510125556.c4df10c1.pws@xxxxxxx>
On Thu, 10 May 2007, Peter Stephenson wrote:
Timo Aaltonen <tjaalton@xxxxxxxxx> wrote:
'unset LANG' doesn't seem to help, and setopt doesn't show multibyte
even if I try to load it. So it somehow fails to load, apparently?
It occurs to me this may simply be confusion because if multibyte is
on by default, it doesn't show up with "setopt" because that shows options
changed from the default. Try also "setopt kshoptionprint". Then you
should be able to see the state of multibyte with a further "setopt". It
should now show up as "nomultibyte off", i.e. no change from the default
state of multibyte on.
That's right, it shows "nomultibyte off".
(If that's not the problem: check that
#define MULTIBYTE_SUPPORT 1
is present in config.h. If that's the case, multibyte support should be
compiled into the main shell and turned on by default. Does "setopt
multibyte" give an error? I presume it doesn't, but if it does, it may be
the wrong version of the shell.)
Doesn't give any error.
If that's all it is, and multibyte mode is on, see if something brutal does
(unset LANG; unset -m 'LC_*'; export LC_ALL=fi_FI.UTF-8; zsh -f)
no change :/
Messages sorted by: