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
ℹ: I will be used Kubernetes example in this issue.
So, notice that we always have to see that module till manually disabled from file by hand. Even we really do not need to see it, use it, etc, we really need a toggle function in Advanced Configuration.
on ⛵ dev-stage-local.idc (dev) ~/.config took 3m6s
It is really annoying that every time we have to see this. Just instead of: ~/.config Isn't it? Thus, ever time when I need to see more information about that specific module, I have to toggle disabled flag in configration file.
Which means that, this module should always be started as disabled when terminal being started, as you think.
If we want to start dealing with some Kubernetes stuffs any time, any where, we can simply call k8s!alias, in order to toggle (disabled=!disabled) that module's active status for current terminal session only.
The text was updated successfully, but these errors were encountered:
I think this might be the same issue as #894? @Dentrax would that solve this issue for you?
Hmmm, exactly. +1 Is this feature in your backlog?
Yep this is in the backlog but I'm not aware of anyone who is working on it at the moment. To avoid having this duplicate issues I'm going to close this issue.
Feature Request
Is your feature request related to a problem? Please describe.
Let's imagine we have a custom
starship.toml
configuration like this:ℹ: I will be used Kubernetes example in this issue.
So, notice that we always have to see that module till manually disabled from file by hand. Even we really do not need to see it, use it, etc, we really need a toggle function in Advanced Configuration.
It is really annoying that every time we have to see this. Just instead of:
~/.config
Isn't it? Thus, ever time when I need to see more information about that specific module, I have to toggledisabled
flag in configration file.Describe the solution you'd like
What about Toggle Aliases?
Which means that, this module should always be started as disabled when terminal being started, as you think.
If we want to start dealing with some Kubernetes stuffs any time, any where, we can simply call
k8s!
alias, in order to toggle(disabled=!disabled)
that module's active status for current terminal session only.The text was updated successfully, but these errors were encountered: