From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 45052@debbugs.gnu.org, philipk@posteo.net
Subject: bug#45052: 27.1; GDB completion moves point
Date: Sat, 05 Dec 2020 18:01:52 +0200 [thread overview]
Message-ID: <83tut0b5sf.fsf@gnu.org> (raw)
In-Reply-To: <6a7e79eb-a705-5cc8-3209-90ab061b4899@gmx.at> (message from martin rudalics on Sat, 5 Dec 2020 16:21:15 +0100)
> Cc: 45052@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 5 Dec 2020 16:21:15 +0100
>
> > 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.
>
> There is `set-window-buffer-start-and-point' for this purpose but it is
> not used by `display-buffer'.
OK, thanks.
> I'm afraid that with these new completion frameworks proliferating
> we may have to check our sources for more incarnations of
> `set-window-start/-point' couplings that do not set NOFORCE.
Maybe we should teach these functions to set the optional_new_start
flag of the window, not only the force_start, given some special value
of NOFORCE. That'd be the next thing I'd try if Philip (or someone
else) reports some adverse effects from the simplistic change I
proposed.
next prev parent reply other threads:[~2020-12-05 16: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.
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tut0b5sf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45052@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.