From 5e29dc321ec2ac6206f259d215f95758e7a64a89 Mon Sep 17 00:00:00 2001 From: shoshin Date: Fri, 1 Jul 2022 23:33:31 -0500 Subject: Docs: [consult] project buffer notes --- shoshin-config.org | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'shoshin-config.org') diff --git a/shoshin-config.org b/shoshin-config.org index 3b16110..336b5a9 100644 --- a/shoshin-config.org +++ b/shoshin-config.org @@ -280,6 +280,21 @@ the new. it seems like consult does this as well as switching themes how do project buffers get filtered? i'm seeing buffers assigned to a project that in my mind, shouldn't be. +looks like it interfaces with ~project-switch-to-buffer~ which has its own +logic about which project a buffer belongs to. some of the mistakes i was seeing +earlier were simply due to starting a repl in a particular directory. + +it appears that "special" buffers may get assigned to a particular project as +well. for example the EWW buffer is part of a project, but it is unclear as +to why. appears likely to have to do with the behavior of the ~default-directory~ +variable which is buffer-local. + +i may want to figure out ways to mark "special" buffers as having a non-project +default-directory set so they don't show up, or just filter them out if it +becomes annoying. i'm accustomed to ~perspectives~ provided by a MELPA package +that hooked into ~projectile~'s project definitions. it would keep a list of +perspective-local buffers where the perspective was tied to a project. + ** embark #+begin_src emacs-lisp -- cgit v1.2.3