6it works but not as advertised (to me) so i think im doing something wrong.
0. Installing (via user) appears to do nothing. upon executing todo i get a bash command not recognized
1. todo is not found with standard ls in /usr/bin
2. will work if the complete *.appimage is ./
3. upon extracting the container (.appimage) and running it without ./ it works as well
4. so just cp or mv?
5. i hope this helps,....
6. <----- eat the mint u un friendly swell
7. nope rated 9 GOTO 9
Please excuse me if I tell you something you already know, but I'd like to help you resolve this issue and I have to work out some details....
AppImages can be anywhere in $PATH or ran from a direct path, but the normal way to use AppImages is via the AppImageLauncher Daemon which defaults to watching ~/Applications and normal $PATH or a path can be set and if you install it here via the OCS-URL method it should be installing it to ~/.local/bin which is usally in path (You can rename the AppImage to anything you want, of course). If you don't rename it you have to exectute it by its full name (E.G. todo-x86_64.AppImage), but that's why I rename most of my AppImages. So, if you just ran it specifically as 'todo' it probably wouldn't work if you haven't renamed it you have to execute 'todo-x86_64.AppImage' if it's in $PATH or /path/to/the.AppImage etc..., but like I said. I just rename it to 'todo'. This is not only an AppImage is why the 'todo --help' might confuse some, I'll clarify in the README later. The is only the AppImage version Sorry for any confusioin and I hope this helps. Let me know.
Ratings & Comments
2 Comments
6 it works but not as advertised (to me) so i think im doing something wrong. 0. Installing (via user) appears to do nothing. upon executing todo i get a bash command not recognized 1. todo is not found with standard ls in /usr/bin 2. will work if the complete *.appimage is ./ 3. upon extracting the container (.appimage) and running it without ./ it works as well 4. so just cp or mv? 5. i hope this helps,.... 6. <----- eat the mint u un friendly swell 7. nope rated 9 GOTO 9
Please excuse me if I tell you something you already know, but I'd like to help you resolve this issue and I have to work out some details.... AppImages can be anywhere in $PATH or ran from a direct path, but the normal way to use AppImages is via the AppImageLauncher Daemon which defaults to watching ~/Applications and normal $PATH or a path can be set and if you install it here via the OCS-URL method it should be installing it to ~/.local/bin which is usally in path (You can rename the AppImage to anything you want, of course). If you don't rename it you have to exectute it by its full name (E.G. todo-x86_64.AppImage), but that's why I rename most of my AppImages. So, if you just ran it specifically as 'todo' it probably wouldn't work if you haven't renamed it you have to execute 'todo-x86_64.AppImage' if it's in $PATH or /path/to/the.AppImage etc..., but like I said. I just rename it to 'todo'. This is not only an AppImage is why the 'todo --help' might confuse some, I'll clarify in the README later. The is only the AppImage version Sorry for any confusioin and I hope this helps. Let me know.