Īn data de 14/09/2001, 00:29:45, Dominik Vogt a scris:
> > >
> > > Look for differences in environment variables. $LANG and $LCxxxx.
> > >
> >
> > Where shall I look for that? I know about the $LANG and $LC_xxxx
> > in my shell (in my .cshrc), I put that. How I know which
> > environment variables are available for a command launched from
> > a fvwm menu?
>
> Just add the command
>
> set > /tmp/environment.$$
>
> to the shell script. This dumps the whole environment of the
> script into the file /tmp/.environment.<process_id>. Do this for
> both types of xterm and compare the output.
>
I just did that and now I understant even less...
diff environment.17839 environment.17844 (xterm versus fvwm)
< HOSTTYPE=i386-linux
> HOSTTYPE=i386
< LANG=ro_RO
> LANG=C
< MACHTYPE=i386
> MACHTYPE=i386-pc-linux-gnu
< OSTYPE=linux
> OSTYPE=linux-gnu
So, the script running from the fvwm menu is in fact running
with LANG=C. Well that is strange, because C means ASCII, 7bit
and shouldn't work. If I change LANG=C in a xterm and I run
the script I get a xterm where the name has no strange characters,
and all 8bit characters can be typed. If now I add
export LANG=C and/or setenv LANG C in my script then it is not
working.
I should manage now to make it work, thank you.
Still, why LANG=C is OK for 8bit characters, and LANG=ro_RO
(or any other) it is not?
Ionel
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Sep 13 2001 - 19:13:30 BST