From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#59381: Should xref--marker-ring be per-window? Date: Sun, 20 Nov 2022 19:00:49 +0200 Message-ID: References: <86leo6ai85.fsf@mail.linkov.net> <83leo67mbt.fsf@gnu.org> <838rk66r17.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21788"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cc: juri@linkov.net, 59381@debbugs.gnu.org To: Eli Zaretskii , Ackerley Tng Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 20 18:02:49 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 1owniT-0005Ol-G5 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 20 Nov 2022 18:02:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owngm-0004Ae-E5; Sun, 20 Nov 2022 12:01:04 -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 1owngk-00049M-HX for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:01: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 1owngk-00032a-70 for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:01:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1owngk-0001pz-27 for bug-gnu-emacs@gnu.org; Sun, 20 Nov 2022 12:01:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 20 Nov 2022 17:01: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.16689636617047 (code B ref 59381); Sun, 20 Nov 2022 17:01:01 +0000 Original-Received: (at 59381) by debbugs.gnu.org; 20 Nov 2022 17:01:01 +0000 Original-Received: from localhost ([127.0.0.1]:44408 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owngi-0001pa-SG for submit@debbugs.gnu.org; Sun, 20 Nov 2022 12:01:01 -0500 Original-Received: from mail-wr1-f45.google.com ([209.85.221.45]:43679) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owngf-0001oz-LS for 59381@debbugs.gnu.org; Sun, 20 Nov 2022 12:00:59 -0500 Original-Received: by mail-wr1-f45.google.com with SMTP id g12so16621857wrs.10 for <59381@debbugs.gnu.org>; Sun, 20 Nov 2022 09:00:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=DkvEDYHnXIPMeaas1u0Yz2U3TxR/eoFNhWoOp/dzqhs=; b=labkl5z6GamPzQjeu3lpcFkNOOWMvK2WExRAnLONfdjuwrjxyri98/9hAe1x2NhFnS QHhtjQVJcGLPUy+hNWeHWqG9LBG/p3qeYLlJQ/aHW97ym36F5K9MPIGadCezy8q4Jaau DSC1I+CJpomv99ass3RxjoAFC1m0qc3Ns3dlLGw2dBVSyMGOYgJd1Ls0uxTG5UcCv3pf GTZQ9QUm6TY8bPyYjCl7pmELWeEdfAUHwwIPU/+gbzZpgi6OSSSdegm63ImXkhYWNLxd d9gtlmWhplLpV1PLHFn8oY8HA01qs42waYkmk/shHo2e5fk4dO8fBE0dokxIrJK2aqEj c6lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DkvEDYHnXIPMeaas1u0Yz2U3TxR/eoFNhWoOp/dzqhs=; b=ssueQimoWzd0W3Bf+Cd81AET8Gxum6MTKJks5zrJTm0LdmpqW4ON1oqxg8MXWtxaM3 pnWWR7/3VwnyThPy+FnqFzcOT9ZbHW4oj2MnGlZBx4hPses2VY5ejbN4APYElSJBEITG RUmaE80vI+E5afoXlO4XKKIlVZnfS6nrFVxJrJjo0nZzjpnHivTq3AnA9ZgNbbFy1cvZ Hv1lv2u9SU99fCZkrqnFx6H26zHCkn3ggeMtghxpVFU21W1z9QY+dXSktdiBVHKQst/a fcIgKFI+qBordoZuJ2u6rM1ot7Z06DFZajegc4Y+FfTai645hlMn34jLqRTwfZbiUn9D QRpw== X-Gm-Message-State: ANoB5plFh8SUcckIUAflxcTtdZyL4zstW678Er3vZVGN01MAfB5GDYvJ kFV7MENwkKS3uvx2OIYVP+o= X-Google-Smtp-Source: AA0mqf49iMr8m5yNmS0g6PHG1fCPQVoJ1JrEDbLQPXTNUxSOXT2VHted74JArKVulEEo+VP5nxB88w== X-Received: by 2002:a05:6000:60a:b0:241:d4ae:8e3f with SMTP id bn10-20020a056000060a00b00241d4ae8e3fmr1264895wrb.437.1668963651558; Sun, 20 Nov 2022 09:00:51 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id q3-20020adfcd83000000b0022eafed36ebsm9182767wrj.73.2022.11.20.09.00.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 20 Nov 2022 09:00:51 -0800 (PST) Content-Language: en-US In-Reply-To: <838rk66r17.fsf@gnu.org> 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:248438 Archived-At: 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? Both windows get the same history, and then their identities will be tired to the positions on the screen, that's how the user will recognize them. 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.