From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#45052: 27.1; GDB completion moves point Date: Sat, 05 Dec 2020 18:01:52 +0200 Message-ID: <83tut0b5sf.fsf@gnu.org> References: <87czzo71i6.fsf@posteo.net> <831rg4cn2v.fsf@gnu.org> <6a7e79eb-a705-5cc8-3209-90ab061b4899@gmx.at> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31548"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 45052@debbugs.gnu.org, philipk@posteo.net To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Dec 05 17:03:24 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kla1s-00085n-0Y for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Dec 2020 17:03:24 +0100 Original-Received: from localhost ([::1]:54590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kla1q-0004tw-Uv for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Dec 2020 11:03:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41852) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kla1X-0004tm-8Q for bug-gnu-emacs@gnu.org; Sat, 05 Dec 2020 11:03:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36518) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kla1W-0004Hc-9J for bug-gnu-emacs@gnu.org; Sat, 05 Dec 2020 11:03:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kla1W-0003RG-41 for bug-gnu-emacs@gnu.org; Sat, 05 Dec 2020 11:03:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Dec 2020 16:03:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45052 X-GNU-PR-Package: emacs Original-Received: via spool by 45052-submit@debbugs.gnu.org id=B45052.160718413913161 (code B ref 45052); Sat, 05 Dec 2020 16:03:02 +0000 Original-Received: (at 45052) by debbugs.gnu.org; 5 Dec 2020 16:02:19 +0000 Original-Received: from localhost ([127.0.0.1]:48064 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kla0o-0003QD-NA for submit@debbugs.gnu.org; Sat, 05 Dec 2020 11:02:18 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51746) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kla0n-0003Q1-00 for 45052@debbugs.gnu.org; Sat, 05 Dec 2020 11:02:17 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47456) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kla0h-00042B-0L; Sat, 05 Dec 2020 11:02:11 -0500 Original-Received: from [176.228.60.248] (port=3552 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kla0d-0000sT-01; Sat, 05 Dec 2020 11:02:09 -0500 In-Reply-To: <6a7e79eb-a705-5cc8-3209-90ab061b4899@gmx.at> (message from martin rudalics on Sat, 5 Dec 2020 16:21:15 +0100) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:195039 Archived-At: > Cc: 45052@debbugs.gnu.org > From: martin rudalics > 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.