From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Systematizing back navigation Date: Tue, 21 Nov 2023 19:01:00 +0200 Organization: LINKOV.NET Message-ID: <86msv7xjfz.fsf@mail.linkov.net> References: <87il5vixat.fsf.ref@yahoo.com> <87il5vixat.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14482"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 21 18:13:57 2023 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 1r5UJw-0003aw-7O for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Nov 2023 18:13:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r5UJ1-00023r-Rc; Tue, 21 Nov 2023 12:12:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r5UJ0-0001zz-BA for emacs-devel@gnu.org; Tue, 21 Nov 2023 12:12:58 -0500 Original-Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r5UIy-0003WM-Pq for emacs-devel@gnu.org; Tue, 21 Nov 2023 12:12:58 -0500 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 0746E60007; Tue, 21 Nov 2023 17:12:50 +0000 (UTC) In-Reply-To: <87il5vixat.fsf@yahoo.com> (Po Lu's message of "Tue, 21 Nov 2023 11:45:46 +0800") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=217.70.183.195; envelope-from=juri@linkov.net; helo=relay3-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313119 Archived-At: > Thus instead of implementing and installing a prototype of this at a > venture, I want to ask everyone else's advice, and also for ideas as > regards when and whether this Back mechanism should act as described in > the last paragraph. I'm afraid it's a quite hopeless endeavor to find such a common denominator that would satisfy even a small fraction of users since endless number of navigation spaces might be active at the same time. Much more than even possible for next-error navigation where we struggled to find a way to switch between available navigation spaces. For example, for the Back button my preference is to navigate in the file system: in a file buffer typing the Back button goes to the Dired buffer with point on that file name when the file was visited from Dired, then the next Back button goes up to the parent directory, etc. like in a typical File Manager.