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.devel Subject: Re: pop-global-mark and info buffers Date: Sun, 06 Dec 2020 22:26:37 +0200 Message-ID: <83czzmadfm.fsf@gnu.org> References: <20201206033517.BDF06C218D5@raman-glaptop.localdomain> <83k0tvbi0u.fsf@gnu.org> <24524.61804.293057.859729@retriever.mtv.corp.google.com> <83sg8j9bww.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4459"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 06 21:29:27 2020 Return-path: Envelope-to: ged-emacs-devel@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 1km0et-00013V-Hr for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 21:29:27 +0100 Original-Received: from localhost ([::1]:41052 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1km0es-0000Oy-FM for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 15:29:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58244) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1km0cO-000869-Tp for emacs-devel@gnu.org; Sun, 06 Dec 2020 15:26:52 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41921) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1km0cO-0006qc-Lr; Sun, 06 Dec 2020 15:26:52 -0500 Original-Received: from [176.228.60.248] (port=2458 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1km0cL-0003Ic-6Y; Sun, 06 Dec 2020 15:26:52 -0500 In-Reply-To: (raman@google.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:260456 Archived-At: > From: "T.V Raman" > Cc: emacs-devel@gnu.org > Date: Sun, 06 Dec 2020 12:15:45 -0800 > > Eli Zaretskii writes: > > Thinking more about this: > > 1.As a long time Emacs user, I suspect I almost never set the mark in > info buffers which is likely why I never got bitten by this. > > 2. The mark ring -- both local and global mark rings are powerful > features but not very approachable to a new Emacs user, and this > specific bug likely will drive at least some of them away. > > 3. The fix to the error message will help, but it may be possible to > do more for the user, e.g. if the marker is outside the narrowed > portion of a buffer, widen and then jump there? We could also > special case info so that we widen, jump and narrow to the node > containing the marker. > > 4. If we dont do 3, perhaps we could in the least jump to the > buffer containing the mark, and change the error to a warning > message that tells the user to widen the visible portion of the > buffer and then tell him how to jump there after widening There's a variable widen-automatically, did you try to use it?