On 2022-12-02, Bram Moolenaar wrote: > Gary Johnson wrote: > > [...] > > > > I assume that mintty can't handle the escape sequences that do work for > > > xterm. To find out which one please use a log: > > > > > > vim -N -u NONE -i NONE --log logfile --cmd 'set bg&' > > > > > > Around where you type the edit command you should be able to find some > > > "raw key input:" and "raw terminal output:" lines that hopefully provide > > > more information. > > > > I did that with TERM=xterm-256color and TERM=mintty and used vimdiff > > to compare the two logfiles. I found the offending escape sequence, > > but I don't know what it means. > > > > When TERM=xterm-256color, at the end of the "raw terminal output:" > > line that prints the introductory message is the sequence > > > > ^[[?4m > > > > I looked in the xterm source, in the file ctlseqs.txt, but could not > > find that sequence, i.e., CSI ? ... m. > > This is a new escape sequence that xterm version 377 supports. It is > used to request the current modifyOtherKeys state. It was supposed to > not do anything for existing terminals. It is documented here: > https://invisible-island.net/xterm/ctlseqs/ctlseqs.html > Search for "XTQMODKEYS".
Ah. I didn't think about it being a new escape sequence so I looked in the source code I had on hand, which was for version 370. Thanks for the link. > I looked at what appears to be the page that explains escape sequences > for Mintty: https://github.com/mintty/mintty/wiki/CtrlSeqs > I cannot find this escape sequence there. Does this happen > accidentally? You could ask the mintty project about it. I didn't see it there, either. [...] > > I would still like to know what that escape sequence is supposed to > > do. If mintty's response seems to be a bug, then I'll report it to > > the author. > > It would certainly be good to know if mintty intentionally uses this CSI > code for something. It is unexpected, perhaps even a bug. I've submitted a bug report to the mintty project, issue #1189. Regards, Gary -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20221203002925.GE16317%40phoenix.
