Feature request: give consult-buffer the ability to only consider visibility in the current frame #1082
WJCFerguson
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
Hi! I have a similar problem myself with EXWM where I want to use different tabs independently. See also #1009. However I am not yet sure about the optimal solution, which is flexible enough for the huge variety of possible use cases, where buffers should be organized by frames/tabs/projects/whatever. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Good point on more use cases. Perhaps an ability to swap in a function alternative to the call to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I drop emacs frames in various Window Manager workspaces and would like them to act more independently with respect to switching buffers. As it is, the sort will bury buffers that are visible in a frame in another WM workspace (even if they're not on screen).
I would submit a PR but I'm pretty unsure about what is the right way to do it. I hacked it for my personal use by copying
defun consult--buffer-sort-frame-visible
from the...-sort-visible
defun so it callsget-buffer-window
with(selected-frame)
as its third arg, and then tweakingconsult--source-buffer
to makeconsult--buffer-query
use that sort function.Beta Was this translation helpful? Give feedback.
All reactions