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
in my opinion, it would be better to use "hamster" instead of "hamster-gtk" for the default appdirs.
This allows people to easily use/try out different hamster clients without changing their options.
The more common use case I can think of are people alternating between using the gui or the cli.
At the moment, people using hamster-gtk but then switching to hamster-cli would be presented with an empty database before switching their options.
If you agree to this notion, I'd be happy to prepare PRs for hamster-gtk and hamster-cli.
Greetings
The text was updated successfully, but these errors were encountered:
this is definitely something that needs to be addressed and I got it on my radar for a while. The current situation however is somewhat deliberate to keep different clients separated as much as possible during development right now.
Once we are preparing the first major release this will need to be revisited and consistent approach to be chosen.
Hi @Takios
I just wanted to reference this comment in a slightly different context that may shine some light on how I personally this we should handle this.
Hey,
in my opinion, it would be better to use "hamster" instead of "hamster-gtk" for the default appdirs.
This allows people to easily use/try out different hamster clients without changing their options.
The more common use case I can think of are people alternating between using the gui or the cli.
At the moment, people using hamster-gtk but then switching to hamster-cli would be presented with an empty database before switching their options.
If you agree to this notion, I'd be happy to prepare PRs for hamster-gtk and hamster-cli.
Greetings
The text was updated successfully, but these errors were encountered: