all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: juri@linkov.net, ackerleytng@gmail.com, 59381@debbugs.gnu.org
Subject: bug#59381: Should xref--marker-ring be per-window?
Date: Mon, 21 Nov 2022 15:14:39 +0200	[thread overview]
Message-ID: <838rk44fgg.fsf@gnu.org> (raw)
In-Reply-To: <c0a9366c-a18a-2d38-416b-a4a164e39537@yandex.ru> (message from Dmitry Gutov on Mon, 21 Nov 2022 01:17:02 +0200)

> Date: Mon, 21 Nov 2022 01:17:02 +0200
> Cc: 59381@debbugs.gnu.org, ackerleytng@gmail.com, juri@linkov.net
> From: Dmitry Gutov <dgutov@yandex.ru>
> 
> On 20.11.2022 09:59, Eli Zaretskii wrote:
> 
> >> 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.

> Or does it apply to the current window? What about the windows split 
> from it? What about older windows we decide to pop-to-buffer to from one 
> of the new windows?

In my mental picture, the stack is not specific to a window, like it is
today.

> >> In my workflow, a new stack is more or less created implicitly by
> >> splitting a window, and discarded by deleting 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?

> Whether M-. pop a new window, or you use project-find-regexp, we usually 
> make sure that after you navigate to a location, it's displayed in the 
> same window the search was made in. Unless the user called something 
> like xref-find-definitions-other-window, naturally.
> 
> So it's generally possible to stay within the same window most of the time.

Not if I split that one window because I want to look at something else as
well.

> And you make good points: Emacs often makes you go from a window to a 
> window, reusing older windows as well. So I'm not sure how to solve that 
> better: searching the window hierarchy won't help.
> 
> So it could be some propagation mechanism working when windows are split 
> or buffers get displayed, which would nevertheless leave a window when 
> the user pressed 'q', for instance. Reverting the window to its previous 
> stack, let's say. And as for separate command, using it explicitly by 
> itself is easy to forget, but it perhaps could be added to some other 
> commands by the user (via before-advice or etc), to mark the beginning 
> of each stack.
> 
> This is a very rough idea. There's nobody to work on it in the near 
> future, I'm afraid, so adding an optional change in behavior to use 
> window-local storage is probably the best way forward. To get feedback, 
> as Ackerley said.

When this becomes practical, we could try it and see if enough people like
it.





  reply	other threads:[~2022-11-21 13:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  5:29 bug#59381: Should xref--marker-ring be per-window? Ackerley Tng
2022-11-19 18:53 ` Juri Linkov
2022-11-19 19:53   ` Eli Zaretskii
2022-11-19 22:01     ` Ackerley Tng
2022-11-20  7:09       ` Eli Zaretskii
2022-11-20 17:00         ` Dmitry Gutov
2022-11-20 17:32           ` Eli Zaretskii
2022-11-20 18:11             ` Ackerley Tng
2022-11-20 18:22               ` Eli Zaretskii
2022-11-20 23:01                 ` Dmitry Gutov
2022-11-21  7:42                   ` Juri Linkov
2022-11-24  3:16                     ` Dmitry Gutov
2022-11-20  2:52     ` Dmitry Gutov
2022-11-20  7:59       ` Eli Zaretskii
2022-11-20 23:17         ` Dmitry Gutov
2022-11-21 13:14           ` Eli Zaretskii [this message]
2022-11-22  2:46             ` Ackerley Tng
2022-11-24  3:28               ` Dmitry Gutov
2022-11-24 14:17                 ` Dmitry Gutov
2022-11-24 23:42                   ` Ackerley Tng
2022-11-24 23:59                     ` Dmitry Gutov
2022-11-25  0:28                       ` Ackerley Tng
2022-11-25  1:02                         ` Dmitry Gutov
2022-11-24  3:19             ` Dmitry Gutov
2022-11-24  7:30               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838rk44fgg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59381@debbugs.gnu.org \
    --cc=ackerleytng@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=juri@linkov.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.