Open Mattwmaster58 opened 1 month ago
I had this idea at some point, and also for the search terms already searched. It's not out of the table, but I ended-up not caring much about it.
Did you know you can use --workspace
, --paths
and --patterns
in order to set an initial state? In my case, I have either a shortcut in my taskbar or a .bat
file that fills the values appropriately based on the project.
I did not know about those flags, thanks for the headsup, that's probably perfect for my needs.
I think a save-last-path approach would cover the majority of cases, but this is based on...nothing at all but a guess ;)
The idea I had for a long time was more an idea of a "project" where you have the necessary configs for a given workspace.
Also, one of the issue with saving the last state is for one that I don't want to write that in the config file. Imo, the config file should be sharable and shouldn't contains this kind of info. And second, it means that you're now leaving artifacts on the computer, so there is a bit more of a concept of uninstalling the software.
The advantage of having this idea of a project, is that you can always create two files where the user specify the project, one for the config and one for the "persistent state". That's for instance how Sublime Text does it.
Anyway, I think it's a good idea.
Another piece of state that would be nice to remember would be the window position :)
I find this app very useful, I use it almost every day. When starting it, the default Paths input value is my AppData directory, and I always need to change it to my monorepo directory. I think it would be useful to retain state beteen opening+closing the application. At minimum, I think just keeping paths would improve the experience a lot, but other inputs could make sense as well (eg Context)