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: Sun, 20 Nov 2022 19:32:20 +0200 Message-ID: <83y1s54jmj.fsf@gnu.org> References: <86leo6ai85.fsf@mail.linkov.net> <83leo67mbt.fsf@gnu.org> <838rk66r17.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8404"; 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 Sun Nov 20 18:33:27 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 1owoC6-00022d-7U for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 20 Nov 2022 18:33:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owoBj-0003hd-6i; Sun, 20 Nov 2022 12:33:03 -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 1owoBi-0003gd-8z for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:33:02 -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 1owoBh-0000lB-Vo for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:33:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1owoBh-0002l2-Rv for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:33: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: Sun, 20 Nov 2022 17:33: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.166896554810560 (code B ref 59381); Sun, 20 Nov 2022 17:33:01 +0000 Original-Received: (at 59381) by debbugs.gnu.org; 20 Nov 2022 17:32:28 +0000 Original-Received: from localhost ([127.0.0.1]:44487 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owoBA-0002kG-BH for submit@debbugs.gnu.org; Sun, 20 Nov 2022 12:32:28 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42336) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owoB7-0002jy-SR for 59381@debbugs.gnu.org; Sun, 20 Nov 2022 12:32:26 -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 1owoB2-0000ii-6m; Sun, 20 Nov 2022 12:32:20 -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=7hmYGMfw/iLDhjc1e250dUVdSNMJupppwbOFx2bnVpw=; b=Uui5LPIsjPtN PKGFo1sFRqz6ObqbvXyjZ7vWmqMvezQGcVMJvqyXWjEgRjQ/vYK8fmfAKb+X1VWWdrFyauJo8xTgd Cikn+NVBduQNJ8ceuR5vCzi8EKS4XoOl+7mK2AQlorTmry/rybqdOK9CRMkrwBYz0gu2Jiy1NYZMn izQzqm/dpMHNMcMa9eD09wGITtX+6WMw+AQdXiMES7xg1APJavQY1Z5Dr/6AlkmZurCj0tSiKA9zq bHEjclQirbWo3U+omZo7tdjyPpbKyubGkzFtD33UfhqU0WHZlSBBHB9FLAVk4MQldqk52I1lp4iM/ PGh5R8dQmHW9SGY3wvt+sw==; 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 1owoAt-0001ih-SS; Sun, 20 Nov 2022 12:32:19 -0500 In-Reply-To: (message from Dmitry Gutov on Sun, 20 Nov 2022 19:00:49 +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:248441 Archived-At: > Date: Sun, 20 Nov 2022 19:00:49 +0200 > Cc: 59381@debbugs.gnu.org, juri@linkov.net > From: Dmitry Gutov > > On 20.11.2022 09:09, Eli Zaretskii wrote: > >> From: Ackerley Tng > >> Date: Sat, 19 Nov 2022 14:01:52 -0800 > >> Cc: Juri Linkov,59381@debbugs.gnu.org > >> > >> What if we copy the whole stackv from the old window whenever a new window is opened? > > What will happen with that if you switch to another window which displays > > the same file, or delete the window where the stack is kept? > > > > And please note that results of creation and deletion of windows are not > > always predictable from the user POV. E.g., when you type "C-x 2", do you > > always know which of the two windows will keep the ID of the original single > > window? > > If the stack is copied, isn't that a non-issue? It is, provided that copying is indeed what the user wants. But how can we know? A new window can be completely unrelated. And I'm more worried by window deletion than by creation. > And FWIW, in my personal config the stack isn't even copied. Somehow > that works out fine, with one small (but potentially significant) caveat > that in my config 'C-x 2' and 'C-x 3' always select the new window. > Making it obvious which of the windows in new, and thus isn't expected > to have existing history. I don't see how this could work reliably enough. Maybe I'm missing something.