Replies: 2 comments
-
|
I've been meaning to do something like that, so I'll accept a PR for it if you or somebody gets to it before I can. That said, it mustn't depend on projectile (I plan to replace it with project.el), and it should only refresh visible buffers immediately and queue buried buffers for when they're next focused or switched to (there could be dozens, even hundreds of buried buffers is a project, and whether or not they're local or remote, that number of blocking |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good! I am looking forward to the switch to project.el. In the meantime, how can we use project.el's API while everything is still projectile? I tried using some project functions and they all failed, but maybe I need to play around with it a bit more |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, the current doom behavior when staging/unstaging/etc. in magit and then switching back to a code buffer is that vc-gutter only updates when the next buffer modification happens.
I think it is reasonable to update vc-gutters when magit operations happen in the same project. I thus have the following code in my configuration:
If there is concern about performance with Tramp + many buffers open, the updates could also be stored in a list and could happen when the buffer is next visited.
Is this something that could become part of Doom?
Beta Was this translation helpful? Give feedback.
All reactions