Subject: Re: bug#73813: 30.0.91; icomplete-mode keymap unusable in xterm for for/backward completions

From: Robert Pluim <[email-masked]>
Date: Wed, 16 Oct 2024 15:58:29 +0200

>>>>> On Wed, 16 Oct 2024 13:03:22 +0000, Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <[email-masked]> said:

    Van> There seems to be a problem for emacsclient in the xterm.

    Van> The "modifyOtherKeys: 1" xresource setting results in emacs receiving

    Van>  ";5;44~" for C-, and 
    Van>  ";5;46~" for C-. when wanting to cycle the icomplete completions

    Van> To demonstrate,

    Van>  # start graphical UI emacs from shell prompt

    Van>  1. start, emacs --init-dir=/path/name
    Van>  2. use, M-x server-start
    Van>  3. use, M-x icomplete-mode

    Van>  # at a second xterm

    Van>  x. start from wrapper script, 
    Van>     env TERM=vt100 emacsclient -f "/path/name/server/file" -ta "" "$@"
    Van>  y. M-x man RET fe
    Van>  z. use C-, and C-. shows,
    Van>     Manual entry: fe;5;44~;5;46~ [No matches]

Well yeah: youʼre telling emacsclient itʼs running in a VT100, so emacs
never sets things up to look for the xterm-specific key sequences.

Robert
--