New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to set the --user flag as default #3552
Comments
If the system installation is empty, you should be able to leave off |
Yes, I removed system apps and now it implicitely use |
I have the same problem but it still ask for user or system choice. |
@rezad1393 use |
I'd really like to be able to do |
Not sure what Flatpak version you're on but the expected behavior is that the |
Uhh, you're right. Sorry about that. It just gives a confusing message when the branch is not matched, e.g.
|
Yeah that's confusing, added a comment to #3996 |
I've noticed an undesirable case when trying to install like this:
It defaults to |
Another example:
Expected result: It should default to Actual result: It defaults to |
https://docs.flatpak.org/en/latest/using-flatpak.html
where is the behaviour above documented? The flatpak website seems to say |
You mean which flatpaks command has no support for All where it makes no sense. Look at |
No, the documentation suggests This thread seems to say I can or cannot use
This isn't documented anywhere that I could see, except here. (if it is feel free to point me there) |
Flatpak 1.12.7 |
Well, $ alias flatpak='flatpak --user'
$ flatpak install flathub xx.xx.xx |
Now try to run |
Everything seems to be ok? |
Good for you. $ LANG=C flatpak --user ps
error: Unknown option --user |
Kinda weird:( |
Expected because |
Maybe this hack will only work in specific versions |
I find myself always installing/managing flatpak apps as user apps.
Is there a way to configure the --user flag as default instead of --system ?
I understand an shell alias could do the trick, but it would be cleaner if set directly on flatpak config IMHO.
If such a feature does not exist, please consider this ticket as a feature request.
The text was updated successfully, but these errors were encountered: