The culprit is tcsh, not XTerm. With bash, Alt-Shift-P produces a
colon.
I added this to my .XDefaults
xterm*altIsNotMeta: truexterm*altSendsEscape: true
so that Alt-Shift-P becomes ESC-P. The problem now does not occur in
tcsh.
Thanks to the correspondents on the list.
On Sat, 2023-10-14 at 15:49 +0200, to...@tuxteam.de wrote:
> On Sat, Oct 14, 2023 at 08:38:22AM -0400, Greg Wooledge wrote:
> > On Sat, Oct 14, 2023 at 07:07:57AM +0200, to...@tuxteam.de wrote:
> > > On Fri, Oct 13, 2023 at 01:06:20PM -0700, Van Snyder wrote:
> > > > I haven't figured out how to unlock the XTerm after
> > > > accidentally givingit Alt-Shift-P.
> >
> > I'm not seeing whatever it is you're seeing here. On Debian 12, if
> > Ilaunch an xterm (simply "xterm &") with bash running inside it,
> > andpress Alt-P I get this character: ð
> > Shift-Alt-P gives me this character: Ð
>
> Oh, that's interesting. Our setups seem to differ in some way.What I
> see with AltGr (not Alt) is Þ, with shift it's þ (thisis Thorn; you
> are seeing eth)
> It seems that your left alt isn't doing Meta and mine doesor
> something :)
> [...]
> > > The behaviour [of Alt-Shift-P] is the same if I do "ESC P". Does
> > > that "hang yourXterm", too?
> >
> > Looks like your bash is in emacs (default) mode. Pressing Esc P
> > inemacs mode triggers this guy:
>
> It is.
> > "\eP": do-lowercase-version
>
> Well, we were talking about the uppercase one (remember: alt-
> shift),so it is this:
> > "\ep": non-incremental-reverse-search-history
> > non-incremental-reverse-search-history (M-p) Search
> > backward through the history starting at the current
> > line using a non-incremental search for a string
> > supplied by the user.
> > I'm not 100% sure what that means, but maybe you can figure it out
> > ifyou continue experimenting with it. I don't normally run bash in
> > emacsmode myself, so many of these readline features are foreign to
> > me.
>
> I tried to describe what it does, and yes, this matches the
> behaviourpretty well: readline (I suppose) prints a colon (I guess
> this is meantas a prompt), you may enter some string, and then it
> searches back inthe history for the last matching command -- so like
> an incrementalbackward search without the incremental bit :-)
> > Anyway, all of that's an interesting tangent, but I still don't
> > geta "freeze" in xterm from any of this.
>
> Absolutely. To both.
> > Van Snyder, can you try running this in your xterm:
> > bind -p | grep P
> > That should tell us whether you have any unusual readline
> > bindingsinvolving the letter P (capital) which might be at fault
> > here. In myshell, I just have these:
> > unicorn:~$ set -o viunicorn:~$ bind -p | grep P"P": self-
> > insertunicorn:~$ set -o emacsunicorn:~$ bind -p | grep P"\C-xP":
> > do-lowercase-version"\eP": do-lowercase-version"P": self-insert
>
> That's what I get too. Now curious as to what Van Snyder gets :-)
> Cheers
