Hello Le 3/9/25 à 23:27, Ingo Schwarze a écrit :
Salut Jean-Michel,BESSOT Jean-Michel wrote on Sun, Mar 09, 2025 at 04:09:17PM +0100:Here the .spectrwm.confIt appears you accidentally sent this file only to me personally instead of to misc@. When you feel very certain which developer is specially interested in a particular topic, it can occasionally be OK to contact that developer directly instead of posting to an OpenBSD list. In this case, however, sending the .spectrwm.conf does not help much because i know nothing about spectrwm, i never used it for anything. Also, there are multiple people on misc@ who replied to your mails. With a problem as complicated and mysterious as the one you found, a list usually results in better chances because more people might have an idea. So please post this file to misc@, ideally restating the problem as cocisely as possible in the mail auch that people don't have to go on a wild goose chase around the thread - e.g. say something like In the xterm+tmux+ksh started by "autorun = ws[1]:xterm -e tmux", accented characters are not displayed; when i change that to "autorun = ws[1]:xterm", they are, and when i then start tmux(1) manually in the resulting terminal, they still are. When i run "xterm -e tmux" manually, they are displayed, too. (If that is what you see - otherwise, describe it correctly!) It might be even better to be slightly more precise: In the case where accented characters do not work, what exactly happens when 1) typing an accented character in that terminal 2) cat(1)ing a file containing an accented character to that terminal Nothing displayed at all? Some escape sequences displayed? Something totally wrong displayed? Even though sthen@ replied to you, do *not* send mail to sthen@ directly because he is doing so much work that he gets easily overwhelmed if people start contacting him directly.# Set the default spawn flags for 'autorun' and 'program' entries. # Note that this does not affect existing entries, including defaults. #spawn_flags = nospawnws autorun = ws[1]:xterm -e tmux #quirk[XTerm:xterm] = XTERM_FONTADJHmmm, this doesn't make it obvious to me what's going wrong. Both "nospawnws" and XTERM_FONTADJ appear to be disabled, and even if they were enabled, i don't see how that would affect what you are seeing. So you might still have to investigate (for example using ktrace(1)) whether spectrwm is really spawning just "xterm -e tmux" or covertly adding some command line options or environment varaibles.
Here the krtace. I hope I did't mess up, it is the first time I use ktrace.
Yours, Ingo
Bye
ktrace.out
Description: Binary data
