unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Philip K." <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45052@debbugs.gnu.org
Subject: bug#45052: 27.1; GDB completion moves point
Date: Sat, 05 Dec 2020 15:01:28 +0100	[thread overview]
Message-ID: <87ft4k73nr.fsf@posteo.net> (raw)
In-Reply-To: <837dpwcqqe.fsf@gnu.org> (message from Eli Zaretskii on Sat, 05 Dec 2020 15:44:09 +0200)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "Philip K." <philipk@posteo.net>
>> Date: Sat, 05 Dec 2020 13:10:46 +0100
>> 
>> 1. M-x gdb
>> 2. Press enter a few times, so that the buffer can't fit into the window
>> 3. Ensure that the point is in the last few lines (C-l)
>> 4. Enter "l" and then press M-tab.
>> 
>> The point should now have been moved. This is not expected, and not seen
>> any other mode.
>
> Does the patch below give good results, and doesn't produce any
> adverse effects in other use cases?

It seems to work, and I can't see any unintended side-effects!

> diff --git a/lisp/progmodes/gdb-mi.el b/lisp/progmodes/gdb-mi.el
> index 9030056..2b9a9c1 100644
> --- a/lisp/progmodes/gdb-mi.el
> +++ b/lisp/progmodes/gdb-mi.el
> @@ -3010,7 +3010,7 @@ def-gdb-auto-update-handler
>         (,custom-defun)
>         (gdb-update-buffer-name)
>         ,@(when (not nopreserve)
> -          '((set-window-start window start)
> +          '((set-window-start window start t)
>              (set-window-point window p))))))
>  
>  (defmacro def-gdb-trigger-and-handler (trigger-name gdb-command
>

-- 
	Philip K.





  reply	other threads:[~2020-12-05 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 12:10 bug#45052: 27.1; GDB completion moves point Philip K.
2020-12-05 13:44 ` Eli Zaretskii
2020-12-05 14:01   ` Philip K. [this message]
2020-12-05 14:26     ` Eli Zaretskii
2020-12-05 14:48       ` Philip K.
2020-12-05 15:03         ` Eli Zaretskii
2020-12-05 15:21           ` martin rudalics
2020-12-05 16:01             ` Eli Zaretskii
2020-12-14  8:23       ` Philip K.
2020-12-14 18:10         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft4k73nr.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=45052@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).