Replies: 2 comments
-
I'm also looking for a way to do this. Coming from Spaceship prompt, I had env variables set to turn off certain modules for large repositories. A simple suggestion would be to allow for directory level config files so that I can override. |
Beta Was this translation helpful? Give feedback.
0 replies
-
There is #4439 which would enable setting config via env vars and therefore would work nicely via direnv and similar solutions which set env vars when you CD into a directory. If you think that would work for you, please leave your thumbs up in the PR :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I wasn't able to find an answer to this in the configuration docs or by searching issues/discussion here.
I have a large network file system that makes multiple modules run very long ex.:
It would be great if I could leave these modules enabled for use elsewhere on my system but have them disabled for a specific root path.
I'm wondering if this is already possible or something that could be added in the future?
Update:
From doing a bit of debugging it would also seem like the directory module should honor both the option
truncate_to_repo = false
as well as disabling the entiregit_
modules when its computing the path here: https://github.com/starship/starship/blob/master/src/modules/directory.rs#L53This appears to be why the directory command takes a full second in this large directory.
Beta Was this translation helpful? Give feedback.
All reactions