3 ms·
I tested the product on both Ubuntu and MacOS, but had a frustrating experience in both cases. I prefer using Fish, but it's not supported. So, I uninstalled i
by vrnvu 3y ago
I tested the product on both Ubuntu and MacOS, but had a frustrating experience in both cases.
I prefer using Fish, but it's not supported. So, I uninstalled it and tried with Bash or Zsh instead.
Even after completely removing Fish from my system, the flow CLI still insists it's there and tries to open a path that no longer exists.
Switching to Zsh gave a different result, but it was still a frustrating experience. While I could activate the flox environment the first time I executed it, exiting caused issues. I had to reactivate it multiple times, encountering errors such as "environment already enabled" before it finally worked properly.
I'm sorry for the negative feedback, but this seems far from a version 1.0 product user experience.
- benfutor 3y agoSorry you had a frustrating experience. It's definitely us missing the mark. Re: fish, saw you found the issue someone else opened on it. We have it on our plan and will be adding support soon https://github.com/flox/flox/issues/1173 https://github.com/flox/flox/issues/1173 Re: your zsh experience, it's hard to judge exactly what's happening from your comment but we have had other users where the state of activation was suppressed by themes which can cause "environment already active". https://github.com/flox/flox/issues/637 https://github.com/flox/flox/issues/637 - if you think it's something else or have more detail to share, let us know (either here, github, anywhere). Thanks for trying Flox! (Flox employee here)
- vrnvu 3y agoThanks for answering. I like the ideas behind nix and flox, and I ack it's not an easy problem. I'll keep my eye on the project and check again in the future. GL.