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
You can currently filter based on global, session, host or directory. I think it would be interesting to also be able to filter on some kind of detected context. For example in the directory of any rust project I am likely to be using cargo a lot but I am unlikely to use it elsewhere. I could use directory filtering, but really it is a lot of directories across different hosts that I would like to have shared context.
Likewise when I am working on Firefox development there are a set of commands that I use all the time there but never anywhere else. I could use directory filtering, but the directories differ between different hosts and again I would like to share across all hosts.
I think the most straightforward way to do this would be by using an environment variable to define the context. So ATUIN_CONTEXT=firefox would select the Firefox context and any commands would have that state stored and when filtering it would default to only show those commands. I could then use direnv or equivalent to set that context whenever I'm in the appropriate directory.
The text was updated successfully, but these errors were encountered:
You can currently filter based on global, session, host or directory. I think it would be interesting to also be able to filter on some kind of detected context. For example in the directory of any rust project I am likely to be using cargo a lot but I am unlikely to use it elsewhere. I could use directory filtering, but really it is a lot of directories across different hosts that I would like to have shared context.
Likewise when I am working on Firefox development there are a set of commands that I use all the time there but never anywhere else. I could use directory filtering, but the directories differ between different hosts and again I would like to share across all hosts.
I think the most straightforward way to do this would be by using an environment variable to define the context. So
ATUIN_CONTEXT=firefox
would select the Firefox context and any commands would have that state stored and when filtering it would default to only show those commands. I could then use direnv or equivalent to set that context whenever I'm in the appropriate directory.The text was updated successfully, but these errors were encountered: