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 04:52:38 +0200 Message-ID: References: <86leo6ai85.fsf@mail.linkov.net> <83leo67mbt.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="37049"; 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: ackerleytng@gmail.com, 59381@debbugs.gnu.org To: Eli Zaretskii , Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 20 03:53:14 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 1owaSI-0009Sf-CC for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 20 Nov 2022 03:53:14 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owaS7-0006wa-R0; Sat, 19 Nov 2022 21:53: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 1owaS6-0006wM-IS for bug-gnu-emacs@gnu.org; Sat, 19 Nov 2022 21:53: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 1owaS6-0008NF-A9 for bug-gnu-emacs@gnu.org; Sat, 19 Nov 2022 21:53:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1owaS5-0002mM-Rb for bug-gnu-emacs@gnu.org; Sat, 19 Nov 2022 21:53:01 -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 02:53: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.166891277210667 (code B ref 59381); Sun, 20 Nov 2022 02:53:01 +0000 Original-Received: (at 59381) by debbugs.gnu.org; 20 Nov 2022 02:52:52 +0000 Original-Received: from localhost ([127.0.0.1]:41930 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owaRv-0002ly-NM for submit@debbugs.gnu.org; Sat, 19 Nov 2022 21:52:52 -0500 Original-Received: from mail-wr1-f43.google.com ([209.85.221.43]:44752) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1owaRr-0002lh-PH for 59381@debbugs.gnu.org; Sat, 19 Nov 2022 21:52:50 -0500 Original-Received: by mail-wr1-f43.google.com with SMTP id v1so15032088wrt.11 for <59381@debbugs.gnu.org>; Sat, 19 Nov 2022 18:52:47 -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=bMzDjYxbfW1gPrUoNvWtOWpbCFP8VZBYzEt/AXvf5fo=; b=pUwfcT8skXkcHkoizeyGZ6QoVowcmDa/96bAxpK8+b/IDnrStB/GlE5WGjNc42PHd+ v3ZOeFerFmoRfqpDbC5w4SCBa2wyKyefGR2lXbw2XvZNlGsbDAte/irJnt5+EFWPBx2d N3AwHxyQFs0sTkaOv9/Bc97PYh6jCDhqCRaHO9K4MkTmsNnB9dgptu2baAT7v7JG+6+q V5nqq4Bf6Eiz5aR+grBzlST2VVaSsupVJr89LiDb9yCJSp0r959/YDl7Xf+mEnjv4c4M S+71R9pwoe3QCSn3hXs3SLYma/MSfXN5eAtG3Sw6AmCcp7RPFHTEXT6DA6C6zOvBqACT YIvw== 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=bMzDjYxbfW1gPrUoNvWtOWpbCFP8VZBYzEt/AXvf5fo=; b=jvBgdd8FKFU8VBAZ0iL5qyClrJs7arKNv5s+XemR20doQH03oqAmx5lPH4tn9wPB7V jhjP7AdawIFADoGttDy5e6KW+RMmKfQeYyaLAiLIQo0T3iKt5vqD7YQJYEWW91ZpYdH0 MAhkfzrU6bGxvugwQbzRa7wnJ+APusQfLT3e+E1fQ/00ZliLHAsebpwW/9R7y0TYKnQp MjHavOeukjnhzmLVC17DYULlWqi2DZnpfJMpD+CKNn3pBLt9CuSCVRjPticKgAfWE1sV LbDrOwb625hoc9SSLo3M9cuIdRbldmR3VHhPTdkbQJ3qPN9aNHkTXTbaQ4IJww5ATA7d kMew== X-Gm-Message-State: ANoB5pnTQqKxXP7iLNDtNWLKUSZcebztAe7qQPVch70aRkq0QPEi74QD yzeKOHQGHhEjYSHk40z5TqI= X-Google-Smtp-Source: AA0mqf6PGdOMwGOJQJBmgmbObYLYmCf5jptUb6x2vYtrO0HL034YEK3ghry34h8/U0+pAfYU55sdYA== X-Received: by 2002:adf:f0ca:0:b0:241:d05a:73e8 with SMTP id x10-20020adff0ca000000b00241d05a73e8mr944566wro.592.1668912761381; Sat, 19 Nov 2022 18:52:41 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id j39-20020a05600c1c2700b003cf57329221sm15095907wms.14.2022.11.19.18.52.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 19 Nov 2022 18:52:40 -0800 (PST) Content-Language: en-US In-Reply-To: <83leo67mbt.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:248387 Archived-At: On 19.11.2022 21:53, Eli Zaretskii wrote: >> Ideally, making an existing variable window-local should be as easy >> as making it buffer-local, e.g.: >> >> (make-variable-buffer-local 'xref--history) >> -> >> (make-variable-window-local 'xref--history) >> >> But we are not here so far. > I don't think it's that simple. Windows are much more ephemeral than buffers; > for example, "C-x 2" followed by "C-x 1" or "C-x 0" deletes one of the windows. > What do we want to happen with the "window-local" xref stack in that case? Poof. Not sure what else we could do. > My guess is that the OP wanted to have control on when M-. pushes locations to > the last used stack or begin a new stack. Because only the user knows when > M-. begins a new series of searches. So I think it is better to offer a > separate command for exercising just such control. As previously mentioned in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38797#8, I personally find it perfectly usable to always use window-local stacks. 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? In my workflow, a new stack is more or less created implicitly by splitting a window, and discarded by deleting one. The older stacks can get forgotten, but while the locations are fresh in mind, this behavior feels logical: it *feels* that I did that chain of navigations in one window, and another in the other one. And I can jump back and forward in each one in parallel. I suppose it doesn't work as well when commands pop new windows a lot, but luckily M-. doesn't do that too often.