GNU bug report logs - #45052
27.1; GDB completion moves point

Previous Next

Full log

Message #20 received at 45052 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Philip K." <philipk <at> posteo.net>, martin rudalics <rudalics <at> gmx.at>
Cc: 45052 <at> debbugs.gnu.org
Subject: Re: bug#45052: 27.1; GDB completion moves point
Date: Sat, 05 Dec 2020 17:03:04 +0200

> From: "Philip K." <philipk <at> posteo.net>
> Cc: 45052 <at> debbugs.gnu.org
> Date: Sat, 05 Dec 2020 15:48:01 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> It seems to work, and I can't see any unintended side-effects!
> >
> > Thanks.  If you use gdb-mi.el a lot, how about if you run with this
> > change for a week and report back if you saw any adverse effects?
> > Then I'll install this if no problems are uncovered.
> 
> Will do. And thanks for finding the bug!

Not a bug, more like an unintended consequence.  The completion
machinery happens in this case to call the gdb-mi handlers for
processing responses to GDB commands, and those handlers force
redisplay to show the GUD window with the same window-start point,
which is impossible when the completions window pops up and point is
close to the bottom of the GUD window.  So I made the window-start
setting less forceful.  My fear is that when those handlers are called
in other situations, you will now see sub-optimal display after
sending GDB commands.  So please pay attention to any such effects on
the gdb-mi related windows.

If my "simple" solution has adverse effects, we will need to come up
with a more thorough one, which will likely require changes on the C
level.

Martin, do we have any way of preventing the original problem via
display-buffer actions, per chance?  I couldn't find anything to that
effect, FWIW.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.