Hi Thomas, On Sat, 28 Feb 2026 14:19:30 +0100 Thomas Wolff wrote: > > Am 27.02.2026 um 18:58 schrieb Johannes Schindelin: > > Hi Takashi, > > > > On Mon, 23 Feb 2026, Takashi Yano wrote: > > > >> Previsouly, CSI6n was not handled correctly if the some sequences > >> are appended after the responce for CSI6n. Especially, if the > >> appended sequence is a ESC sequence, which is longer than the > >> expected maximum length of the CSI6n responce, the sequence will > >> not be written atomically. With this patch, pcon_start state > >> is cleared at the end of CSI6n responce, and appended sequence > >> will be written outside of the CSI&n handling block. > I encounter stray CSI6n when I invoke wsl.exe via execl(p) within a > forkpty child and I was puzzled why that occurs. > Could it be related to this issue (and hopefully fixed by the patch)?
pty sends CSI6n to check if the terminal has CSI6n capability before calling CreatePseudoConsole(). This is because, CreatePseudoConsole() waits for CSI6n response forever so it hangs if terminal does not respond to CSI6n. The check result is cached, so the check will not be done in the second time. Isn't this the 'stray CSI6n'? Do you have any problem with this 'stray CSI6n'? -- Takashi Yano <[email protected]>
