Peter Jonas

@TheAssassin, it's a while since I looked at this. Is the problem that Launchpad doesn't pull in the code for the submodules, so it relies on an ancient version of...

> This issue should not have been dismissed instead of fixed... > you have been unable to actually fix this issue within the last *two months*. This is open source...

@wsbankenstein, well done for trying! Programming isn't easy by any means, but you put the effort in when not everybody would so thanks for that!

@probonopd > Check how it works on the Mac. No such dialogs needed at all. Much more elegant. Not quite true. Double-clicking the `.dmg` brings up a prompt to drag...

> A user never has to click "no" if they don't want anything to be moved or copied They have to close the prompt, which is essentially the same thing....

Bash completions for `myapp` should be: - put in `/usr/share/bash-completion/completions/myapp` - installed to `~/.local/share/bash-completion/completions/myapp` However, before the completions can be used, the user must first load the completion script by...

The completions script for `myapp` will look something like this: ```bash # install this file to '/usr/share/bash-completion/completions/myapp' or similar function _myapp() { # completion logic } complete -F _myapp myapp...

> > Yes. Question: I have 5 different versions of foo installed. Which one will "win" in terms of bash completion? > > Can't this same question be asked for...

@tresf, it's best not to give a full path to `complete`. If you do this... ```bash complete -F _myapp /home/user/Applications/MyApp.AppImage ``` ... then completion will only work when the user...

Since Bash completion scripts run actual terminal commands, patching them can get complicated and could even be considered dangerous! Consider this example: ```bash # install this file to '/usr/share/bash-completion/completions/myapp' or...