3 ms·
You could always just rig up a couple Bash aliases and change where your menu works. Say for example appimg() { chmod +x $1; mv $1 ~/apps/ } and then bind a key
by devenblake 6y ago
You could always just rig up a couple Bash aliases and change where your menu works. Say for example appimg() { chmod +x $1; mv $1 ~/apps/ } and then bind a key sequence to `$(ls ~/apps/ | dmenu)`.
- incrudible 6y agoNot to dismiss your reply, but I've always thought that the "just open the terminal and..." kind of solution that is always brought up is holding Desktop Linux back. There's a workaround for almost everything. Wherever there is a workaround, the problem becomes less severe. As a result, it is less likely to get fixed. There is nothing preventing AppImages to work like app containers on Mac OS except lack of integration that comes out-of-the-box. Advocating for that integration becomes more difficult, when you can "just open the terminal and...".
- vinay427 6y agoI posted this above, but at least for me, this project seems to do the trick: https://github.com/TheAssassin/AppImageLauncher https://github.com/TheAssassin/AppImageLauncher I did use a terminal to install the AUR package on my system, however. ;)