Ionel Mugurel =?iso-8859-2?Q?Ciob=EEc=E3?= <tgakic_at_sg10.chem.tue.nl> writes:
> În data de 13/09/2001, 17:30:04, Dan Espen a scris:
> > Ionel Mugurel Ciobîcã <tgakic_at_sg10.chem.tue.nl> writes:
> > > Hi all,
...
> > > I configured fvwm under Debian to execute some commands
> > > from my ~/bin directory.
> > >
> > > For example small scripts to open a xterm with a rlogin command:
> > > ========cut here========= (~/bin/mail
> > > xhost +bambam.chem.tue.nl
> > > /usr/bin/X11/xterm -bg darkcyan -fg lightyellow -bd blue -cr magenta -sb
> -sl
> > > 1500 -j -ls -fn "-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-
> 16"
> > > -name PO?TA -title PO?TA -e rlogin -8 -l tgakic bambam.chem.tue.nl &
> > > ========cut here=========
> > > In my ~/.fvwm/main-menu.hook I have:
> > >
> > > ========cut here=========
> > > ...
> > > AddToMenu "/Debian/Hosts" "Hosts%mini-telnet.xpm%" Title
> > > + "e-mail%mini-mail.xpm%" Exec exec ~/bin/mail
> > > ...
> > > ========cut here=========
> > >
> > > When I click with the mouse on the "e-mail" I get my xterm running rlogin
> .
> > > The same is happening when I simply call the script from an open xterm.
> > >
> > > But they don't behave the same. My question is why? Two differences are
> > > important. The name of the xterm is not the same. The one called from the
> > > fvwm menu is OK and the other called from a xterm show a square made from
> > > dashed lines, a minus, a capital B and then the 8bit character. This is
> > > the same for any 8bit character.
> >
> > When you start the xterm with -ls it runs you login shell.
> > (Your .profile or .login.) Perhaps something different is
> > happening than when you first log in.
>
> I access the same command from the fvwm menu and from an xterm.
> Yes, the script have xterm -ls, which I know, it reads my .login
> and .cshrc files.
> >
> > The stuff with a capital B indicates a complex string in the
> > title. You need fvwm2.4 built with enable multibyte to display
> > that correctly. The client application (xterm in this case)
> > makes the title string
> > into a complex string. We've found that Java does that based
> > on $LANG or one of the other Locale based environment variables.
> > Perhaps something similar is going on with xterm.
>
> So the problem is with xterm? I don't think so. If I call the same
> script from rxvt, eterm, konsole, the same happened like with xterm.
> The only way to get it right is via the fvwm menu.
I'm not sure if I'd say xterm is doing something wrong.
I don't know if it needs to mark that string as a complex
string to display right. I suspect that it doesn't.
Maybe you want to take the easy way out and download 2.4.0
and compile it with --enable-multibyte and be done with it.
> > > The second difference is that in the xterm opened from the fvwm menu
> > > the input of 8 bit characters are OK, while in the other one only few
> > > are accepted. Example î and â are accepted in both, while ?, ? or ?
> > > are silently ignored. î and â are common in between latin1, latin2
> > > and latin10, ?, ? or ? are not.
> > >
> > > I think that somehow the commands executed via the fvwm menu have a
> > > different environment or something. I can't explain why this is
> > > happening. Can someone gave me a hint in which direction to look for
> > > an answer.
> >
> > 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?
Do this in the xterm to see whats set:
env | grep LANG
env | grep LC
I'm not quite sure what the difference is either.
You might want to put some print statements in your .profile
and .cshrc while you are trying to figure this out.
Do have $SHELL set?
Do you use the fvwm command ExecUseShell?
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
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 - 17:48:58 BST