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

Flatpak Bash autocompletion of app ids should be case-insensitive #2207

Open
fenryxo opened this Issue Oct 7, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@fenryxo

fenryxo commented Oct 7, 2018

Linux distribution and version

Fedora 28

Flatpak version

1.0.2

Description of the problem

Some flatpaks use org.gnome.Capital while the others org.gnome.lowercasename. That makes the autocompletion cumbersome because it isn't case-insensitive.

Steps to reproduce

  1. I want to install Evolution.
  2. I type flatpak install flathub org.gnome.e<Tab> but there is no Evolution
  3. So I need to type flatpak install flathub org.gnome.E<Tab>.

I would expect flatpak install flathub org.gnome.e<Tab> to autocomplete also ids starting with org.gnome.E. Is it possible?

@aiamuzz

This comment has been minimized.

Show comment
Hide comment
@aiamuzz

aiamuzz Oct 7, 2018

this whole reverse dns naming protocol is just too unfriendly and cumbersome ... I know its kind of seems inspired by the reverse domain name structure seen in android apps ... but adopting that on a linux desktop setup where people pride in using the CLI more than gui ... its a really bad idea ... honestly !!!

this protocol being used in android makes sense because nobody uses CLI there ... If flatpak had launched with only a GUI app store for flathub ... it would not have mattered ... but on a CLI preferred operating system ... and the fact that a GUI flathub store is too early to even speak about ... is just not happening !!!

As the flatpak user base grows, the number of people detesting this setup is just going to keep growing ... more people discontent with this naming protocol ... better to deal with it when the user base is still small and forgiving ...

Uniformity and ease of use should be paramount ... in a system that is deep rooted in CLI !!!

aiamuzz commented Oct 7, 2018

this whole reverse dns naming protocol is just too unfriendly and cumbersome ... I know its kind of seems inspired by the reverse domain name structure seen in android apps ... but adopting that on a linux desktop setup where people pride in using the CLI more than gui ... its a really bad idea ... honestly !!!

this protocol being used in android makes sense because nobody uses CLI there ... If flatpak had launched with only a GUI app store for flathub ... it would not have mattered ... but on a CLI preferred operating system ... and the fact that a GUI flathub store is too early to even speak about ... is just not happening !!!

As the flatpak user base grows, the number of people detesting this setup is just going to keep growing ... more people discontent with this naming protocol ... better to deal with it when the user base is still small and forgiving ...

Uniformity and ease of use should be paramount ... in a system that is deep rooted in CLI !!!

@matthiasclasen

This comment has been minimized.

Show comment
Hide comment
@matthiasclasen

matthiasclasen Oct 7, 2018

Collaborator

Please stop harping on the naming. It is not going to change. Flatpak is first and foremost a system to install graphical desktop apps, with good integration in the desktop for installation, updates and launching. The commandline is not where it is taking its design direction from.

Collaborator

matthiasclasen commented Oct 7, 2018

Please stop harping on the naming. It is not going to change. Flatpak is first and foremost a system to install graphical desktop apps, with good integration in the desktop for installation, updates and launching. The commandline is not where it is taking its design direction from.

@matthiasclasen

This comment has been minimized.

Show comment
Hide comment
@matthiasclasen

matthiasclasen Oct 7, 2018

Collaborator

And yes, we can do things like making the completion work better, if case-insensitive matching helps, it is worth considering

Collaborator

matthiasclasen commented Oct 7, 2018

And yes, we can do things like making the completion work better, if case-insensitive matching helps, it is worth considering

@aiamuzz

This comment has been minimized.

Show comment
Hide comment
@aiamuzz

aiamuzz Oct 7, 2018

Please stop harping on the naming. It is not going to change. Flatpak is first and foremost a system to install graphical desktop apps, with good integration in the desktop for installation, updates and launching. The commandline is not where it is taking its design direction from.

@matthiasclasen ... i am sorry its not harping over it ... its expressing the difficulty of use ... just like the case-insensitive matching ...

If the flatpak team really wants this issue, to not be thrown at them repeatedly... its best you open a issue thread explaining why "Its not going to Change" ... a technical explanation which the techy and some layman side notes explanation clarifying the flatpak teams position on this issue

If this naming convention is best ... how ?
and if its a practical difficulty to accomplish a simpler system ... why ?

... I am sure all of us will read it and abstain from raising an issue relating to that topic ... or at best someone might find an elegant solution if its an implementation difficulty !!!

PS : I am not saying it at being rebuked at expressing my experieince ... but more so with the hope that once a clear rationale is provided it will nip the entire topic in the bud !!!

aiamuzz commented Oct 7, 2018

Please stop harping on the naming. It is not going to change. Flatpak is first and foremost a system to install graphical desktop apps, with good integration in the desktop for installation, updates and launching. The commandline is not where it is taking its design direction from.

@matthiasclasen ... i am sorry its not harping over it ... its expressing the difficulty of use ... just like the case-insensitive matching ...

If the flatpak team really wants this issue, to not be thrown at them repeatedly... its best you open a issue thread explaining why "Its not going to Change" ... a technical explanation which the techy and some layman side notes explanation clarifying the flatpak teams position on this issue

If this naming convention is best ... how ?
and if its a practical difficulty to accomplish a simpler system ... why ?

... I am sure all of us will read it and abstain from raising an issue relating to that topic ... or at best someone might find an elegant solution if its an implementation difficulty !!!

PS : I am not saying it at being rebuked at expressing my experieince ... but more so with the hope that once a clear rationale is provided it will nip the entire topic in the bud !!!

@alexlarsson

This comment has been minimized.

Show comment
Hide comment
@alexlarsson

alexlarsson Oct 8, 2018

Member

The application identifier is more than just the name used to start the flatpak, it is also tied to things like the dbus identifier and avoidance of conflicts when exporting things to the system. This has been explained many times, and while it would nice to have a single place to point people to for a description, my experience is that nobody will read that.

Member

alexlarsson commented Oct 8, 2018

The application identifier is more than just the name used to start the flatpak, it is also tied to things like the dbus identifier and avoidance of conflicts when exporting things to the system. This has been explained many times, and while it would nice to have a single place to point people to for a description, my experience is that nobody will read that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment