Re: accented characters not showingutomatically started xterm:

Le 3/7/25 à 23:26, Jan Stary a écrit :
>>> Run env in both and see the difference.
>>> Does the "terminal" (= xterm?) launch a login shell (as in ksh -l),
>>> and thus read your ~/.profile?
>>>
>>> Jan
>>>
>> env from the automatically started xterm:
> What does "automaticaly" mean?
> The X session using yoru WM of choise starts that itself?
> How exactly is that xterm launched?

It it configured in sperctrwm configuration (.sperctrwm.conf). So it is
spectrwm who launch xterm -e tmux.

>
>> jean-mi@x1:~$ env
>> _=/usr/bin/env
>> LOGNAME=jean-mi
>> WINDOWID=8388620
>> WINDOWPATH=5
>> XTERM_SHELL=/bin/ksh
>> HOME=/home/jean-mi
>> _SWM_XTERM_FONTADJ=
>> PWD=/home/jean-mi
>> SWM_STARTED=YES
>> TERM_PROGRAM=tmux
>> LC_CTYPE=fr_FR.UTF-8
>> TERM_PROGRAM_VERSION=openbsd-7.7
>> XTERM_VERSION=XTerm/OpenBSD(395)
>> DISPLAY=:0
>> LANG=fr_FR.UTF-8
>> ENV=/home/jean-mi/.kshrc
>> PATH=/home/jean-mi/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin
>> TMUX=/tmp/tmux-1000/default,51238,4
>> TMUX_PANE=%4
>> TERM=screen
>> SHELL=/bin/ksh
>> _SWM_WS=0
>> USER=jean-mi
>> XTERM_LOCALE=C
>>
>> env from the xterm started after:
>>
>> jean-mi@x1:~$ env
>> _=/usr/bin/env
>> LOGNAME=jean-mi
>> WINDOWID=16777228
>> WINDOWPATH=5
>> XTERM_SHELL=/bin/ksh
>> HOME=/home/jean-mi
>> _SWM_XTERM_FONTADJ=
>> PWD=/home/jean-mi
>> SWM_STARTED=YES
>> TERM_PROGRAM=tmux
>> LC_CTYPE=fr_FR.UTF-8
>> TERM_PROGRAM_VERSION=openbsd-7.7
>> XTERM_VERSION=XTerm/OpenBSD(395)
>> DISPLAY=:0
>> LANG=fr_FR.UTF-8
>> ENV=/home/jean-mi/.kshrc
>> PATH=/home/jean-mi/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin
>> TMUX=/tmp/tmux-1000/default,51238,5
>> TMUX_PANE=%5
>> TERM=screen
>> SHELL=/bin/ksh
>> _SWM_WS=0
>> USER=jean-mi
>> XTERM_LOCALE=C
>> jean-mi@x1:~$
>>
>> I do not see much differences.
> But you have diff(1), right?
>
>> Terms launch tmux.
> What's "Terms"?
It is the terminals.
>
> I am not sure of what you call a Login Shell.
>
> That because you haven't read ksh(1) about -l
>