You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand when using treemacs-follow-mode I have currently two options:
make sure that the file I'd like to open is one of the projects within workspace
use treemacs-display-current-project-exclusively that will only keep open the project that contains currently selected file
What I'd like to be able to do is to treemacs to automatically add to the workspace the project containing the file that I open via whatever means, and potentially later on remove the project after I navigate away from that file
The text was updated successfully, but these errors were encountered:
Sorry, but given the limited time I have now I'm very reluctant to accept non-trivial feature requests. I won't reject this outright, but my current priority is getting through my backlog.
Maybe treemacs-project-follow-mode can do what you want? Other than that I also have plans for an extension that shows your open buffers inside treemacs, similar to what vs code does. This one is at least towards the top of my list.
I'd like to be able to treemacs-find-file that does not fall under any project in the workspace and have a surrounding project opened. I believe follow mode still requires adding the project to the workspace in advance.
This issue has been automatically marked as stale because it has not had recent activity (this bot only works as a reminder, it will not close issues).
As I understand when using
treemacs-follow-mode
I have currently two options:treemacs-display-current-project-exclusively
that will only keep open the project that contains currently selected fileWhat I'd like to be able to do is to treemacs to automatically add to the workspace the project containing the file that I open via whatever means, and potentially later on remove the project after I navigate away from that file
The text was updated successfully, but these errors were encountered: