On Wed, 6 May 2009, Thomas Adam wrote:
2009/5/6 Lucio Chiappetti <lu...@lambrate.inaf.it>:
I have no idea whether fvwm or whatever is the lead X process in the
complex SuSe X login do execute .login.
Nothing in FVWM does -- and no shells do by default. Sort this out by
looking at what your shell is doing when it's invoking a login shell.
A long time ago (soon after I moved to SuSE when I was choosing the window
manager), I tried to trace all the steps of an X login, including the
execution of sytemwide /etc/csh.cshrc /etc/csh.login and user .cshrc and
.login. I still have some obscure notes about it.
I seem to remember there are transient processes involved. This seems
indicated also by the gap in the pid's in the following excerpt of a
tree-like ps.
PPID PID USER COMMAND
1 4971 root /opt/kde3/bin/kdm
4971 4989 root /usr/X11R6/bin/X -nolisten tcp .....
4971 4990 root -:0
4990 6303 lucio /usr/bin/X11/fvwm
6303 469 lucio xterm
469 471 lucio -csh
You should realize that an user of fvwm and csh like me is sort of an
anomaly for SuSE who expects KDE and bash :-)
I believe there is some transient bash involved in the X login.
Anyhow the main question was whether an xterm started via Exec xterm from
a .fvwm2rc menu should behave differently than an xterm started from a
shell.
What happened was that the former has correct unicode support, while the
latter requires an explicit -u8.
Now I've arranged everything, and I'm inclined to "if ain't broken don't
fix it".
But I was just curious if the correct unicode support in the menu Exec
xterm was an fvwm bonus, or just a coincidence of some local setup.
--
Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)
For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
-----------------------------------------------------------------------
"Nature" on government cuts to research http://snipurl.com/4erid
"Nature" e i tagli del governo alla ricerca http://snipurl.com/4erko
