-
Notifications
You must be signed in to change notification settings - Fork 166
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
Reimplement the (deprecated) gtgcli utility's functionality as arguments for the main application #418
Comments
There is no gtgcli in 0.4 release at all, not just missing from flatpak. |
ah good to know.
|
Some reincarnation of this is in the future plans somewhere, perhaps related to #277. In any case, looks like @nekohayo should have a look at this for the website outdatedness |
I can't remember if I put this in a ticket here somewhere, but we should replicate the functionality of gtgcli by adding parameters to gtg itself (now that we can talk to the primary instance thanks to GtkApplication). |
Reopening as an enhancement/feature request with low-hanging-fruit (assuming it's not so hard that it would mean "patch-or-wont-happen") then, rather than a bug/defect. I'm presuming that it could probably be a fun project for a newcomer to implement. It could maybe even be used as a workaround to solve #643, i.e. users could use GNOME Control Center's ability to bind a keyboard shortcut to running a custom command... |
Wiki page has been slightly updated to at least link to here ;) I tried finding which commit removed the gtgcli code to reference it here, but didn't find it during my brief search. If @Neui or @diegogangl remembers how it was called as a commit message and can find it, might be worth mentioning here for the record and as potential code inspiration to people looking at this (even if the new approach based on |
The title pretty much says it all. How does one launch gtgcli after installing GTG via flatpak? "flatpak run" doesn't seem to have any listing for gtgcli. Only GTG.
The text was updated successfully, but these errors were encountered: