Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Definitions: File Name Wildcards and Individual Files #1097

Open
c-alpha opened this issue Mar 27, 2024 · 3 comments
Open

Project Definitions: File Name Wildcards and Individual Files #1097

c-alpha opened this issue Mar 27, 2024 · 3 comments
Labels

Comments

@c-alpha
Copy link

c-alpha commented Mar 27, 2024

Hello, I'd like to be able to use finer controls when specifying what is part of a project, and what isn't. To my understanding, the currently the only option is to use path :: to specify one or more directories?

I have two use-cases where a finer grained control would be handy.

The first one is for picking a small subset of an otherwise densely populated directory:

** Shell Init Files
 - file :: ~/.zshenv
 - file :: ~/.zshrc
 - path :: ~/.zsh
 - file :: ~/.profile
 - file :: ~/.bash_profile

The second one is to white-list a subset by extension:

** My Org Scribe
 - path :: ~/Notes/*.org

It seems to me neither were currently possible? Have I missed the decisive bit of documentation?

@Alexander-Miller
Copy link
Owner

It seems to me neither were currently possible? Have I missed the decisive bit of documentation?

You haven't, treemacs can't do something like this.

While I see the utility a feature of that scope would be a lot work, and my current priority is cleaning up the backlog and fixing bugs, not new large features. I'll leave the ticket open, but I cannot say when I'll have the time to look at it.

@c-alpha
Copy link
Author

c-alpha commented Mar 28, 2024

Thanks for your swift response. I see & understand. Also appreciate your keeping it on the "inspirational backlog"! 👍👍 👋

Copy link

stale bot commented May 28, 2024

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).

@stale stale bot added the stale label May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants