Fork me on GitHub

@gtzogana sometimes I just redefine the test as empty 😄


so it means it still runs but at least it passes quickly


How do I prevent "buffer creep" in the sense that I can dedicate workspaces to only allow buffers to come into view if they are part of a specific project?


projectile-switch-to-buffer might be a good start


I use that all the time, but it's prev-next buffer that isn't aware of projects. I started to look into making a next/previous buffer for projects but wanted to see if there's an equivalent. Basically I want to dedicate a layout to a specific project.


I use such an approach, it works great but it's too tailor-made to share it (yet) Basically I have a hashmap mapping project-id -> filename-list, and my next/prev buffer functions shift the order of those lists by one position


What are some of the vars you use to build the list, if you can could you sahre it in a gist, I'm curious to build on it


I wanted to do something like check if the next buffer was in the same layout, if not then go to the nearest one that was, and vice versa for previous


just found the code for next-buffer pretty involved

vemv13:09:43 • The code uses a fixed layout: (vemv/safe-select-window vemv/main_window). vemv/main_window is the window where I open all my project-specific file buffers (other buffers may temporarily hijack it as well) • Only 3 function calls in this body are relevant to the 'algorithm': (vemv/clean-chosen-file-buffer-order), (switch-to-buffer ..., (puthash ...


Hope it helps!


I'll take a look, thanks