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

[Eli Zaretskii]

> From: Van Ly <van.ly@sdf.org>
> Cc: 73813@debbugs.gnu.org
> Date: Wed, 16 Oct 2024 13:03:22 +0000
> 
> 
> There seems to be a problem for emacsclient in the xterm.
> 
> The "modifyOtherKeys: 1" xresource setting results in emacs receiving
> 
>  ";5;44~" for C-, and 
>  ";5;46~" for C-. when wanting to cycle the icomplete completions
> 
> To demonstrate,
> 
>  # start graphical UI emacs from shell prompt
> 
>  1. start, emacs --init-dir=/path/name
>  2. use, M-x server-start
>  3. use, M-x icomplete-mode
> 
>  # at a second xterm
> 
>  x. start from wrapper script, 
>     env TERM=vt100 emacsclient -f "/path/name/server/file" -ta "" "$@"
>  y. M-x man RET fe
>  z. use C-, and C-. shows,
>     Manual entry: fe;5;44~;5;46~ [No matches]
> 
> 
> The following are scripts for how emacs and emacsclient are launched.
> 
> I wasn't able to use the "emacs -Q" invocation with emacsclient to
> produce the observed unexpected behavior.
> 
> 
> 
> # emacs-30x.sh
> 
> 1 #!/bin/sh
> 2 P=/u/w/src/emacs/build-30-2/src/emacs
> 3 D="/u/w/sys/emacs/30x"
> 4 $P --init-dir="$D"
> 
> # emacsclient-plain-30x.sh
> 
> 1 #!/bin/sh
> 2 P=/u/w/src/emacs/build-30-2/lib-src/emacsclient
> 3 F=/u/w/sys/emacs/30x/server/server
> 4 env TERM=vt100 $P -f "$F" -ta "" "$@"

I don't get it: you tell Emacs that your terminal is vt100, but expect
it to behave as if the terminal were xterm?  Why should it?