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#59381: Should xref--marker-ring be per-window? Date: Thu, 24 Nov 2022 09:30:34 +0200 Message-ID: <83a64gyfl1.fsf@gnu.org> References: <86leo6ai85.fsf@mail.linkov.net> <83leo67mbt.fsf@gnu.org> <83v8na5a5e.fsf@gnu.org> <838rk44fgg.fsf@gnu.org> <7b2b0386-ae47-cdc5-d275-00a678c23b46@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26569"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, ackerleytng@gmail.com, 59381@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 24 08:31:42 2022 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 1oy6hx-0006fi-Qe for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Nov 2022 08:31:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oy6hR-0002zO-L4; Thu, 24 Nov 2022 02:31:10 -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 1oy6hK-0002z7-Cw for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 02:31:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oy6hK-00059Q-4j for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 02:31:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oy6hJ-0003Xp-Li for bug-gnu-emacs@gnu.org; Thu, 24 Nov 2022 02:31:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Nov 2022 07:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59381 X-GNU-PR-Package: emacs Original-Received: via spool by 59381-submit@debbugs.gnu.org id=B59381.166927503013585 (code B ref 59381); Thu, 24 Nov 2022 07:31:01 +0000 Original-Received: (at 59381) by debbugs.gnu.org; 24 Nov 2022 07:30:30 +0000 Original-Received: from localhost ([127.0.0.1]:57056 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oy6gn-0003X2-I2 for submit@debbugs.gnu.org; Thu, 24 Nov 2022 02:30:29 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:50388) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oy6gi-0003Wj-6e for 59381@debbugs.gnu.org; Thu, 24 Nov 2022 02:30:27 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oy6ga-00054i-4q; Thu, 24 Nov 2022 02:30:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=AjPK5jlOWH2D9oEn16WDVWnNVfdVslQCB0Kp1exWY0A=; b=nbbDtjsXFLkA zAkDL/o/IvU81VuwD/cODDU0OkX6Wag0urRj/F1pyH1hu7q+qVvlo6NE6N+GcrYnkMf8xqJ78gV0S x6rctSk8t+NEH6+rFgtByjQMpaoTnsnSyMnKqTfgHN8tJa609qiofBAMFmYRNA15NOlnwUFFY+RPE 9DOVFxMPtkDhmsB0A3DUEZcOSCD6Y9X+tXFDhorat4vWd1aIPxNxqtQdMe+dWY8BoYeV2K8pmRG9i CiaAJwZEExU14+Tcjl/SwaVbcDJ3AsDEOKB1FKna53zPVdQmdbBVq5yuKTJ+ApgQypFYN59Azu/b/ AaHh2gJZloCde31553LUCg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oy6gZ-000225-9I; Thu, 24 Nov 2022 02:30:15 -0500 In-Reply-To: <7b2b0386-ae47-cdc5-d275-00a678c23b46@yandex.ru> (message from Dmitry Gutov on Thu, 24 Nov 2022 05:19:22 +0200) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:248823 Archived-At: > Date: Thu, 24 Nov 2022 05:19:22 +0200 > Cc: 59381@debbugs.gnu.org, ackerleytng@gmail.com, juri@linkov.net > From: Dmitry Gutov > > >>>> But maybe it will be helpful for you to elaborate: what the workflow > >>>> would look like. Would it be a parallel set of commands, or simply a > >>>> command to... do what? > >>> > >>> I just did that, above: add a command that starts a new "stack". All the > >>> rest is unchanged. > >> > >> What would happen with the current stack, though? > > > > It's discarded, as no longer needed. > > That sounds odd. The idea regarding windows is about keeping multiple > stacks at the same time, not about discarding information. My idea is not about windows, though. It's about a workflow that resembles searches: you keep searching for the same or similar strings as long as you are interested in a particular string/regexp; as long as you do that, using "C-s C-s" to repeat search, perhaps with minor edits of the search string, is what you want. Then, when you want another search, you discard the previous search string and start with a completely new one. > >>> So you always ever have a given buffer displayed in a single window? > >> > >> Not necessarily, no. If it's a big file, I can have two parallel > >> "investigations" going on in two different window on it. Using two > >> different navigation stacks. That's a feature. > > > > It's a feature if you indeed want a separate stack in each window. What if > > you want the same stack in all of those windows? > > Maybe you never do? Or if you really do, that would require some > additional manual management (through new commands, I suppose). I do that sometimes, not to rarely to remember it as a feature. That's why I suggested an explicit command, because I don't think Emacs can guess my intentions in this case.