Your message dated Sun, 1 Nov 2015 14:39:28 +0100
with message-id <20151101143928.4a47faeb@busgosu>
and subject line Re: Bug#799846: launchy: problems running complicated scripts
from desktop files
has caused the Debian Bug report #799846,
regarding launchy: problems running complicated scripts from desktop files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
799846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799846
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: launchy
Version: 2.5-3
Severity: minor
Tags: upstream
Dear Maintainer,
it looks like Launchy has problems to launch complex commands from desktop
files. Namely, I have experience these problems:
1) Having a desktop file with Exec definition pointing to home directory using
tilda - e.g. Exec=~/bin/script_name, Launchy is unable to launch the command
(simply hitting Enter on the found item from the list does not trigger any
action). PS: typing ~/bin/script_name directly in the Launchy window, the
script is started. So the problem really seems to be only when combined with a
desktop file.
2) If Exec in a desktop file contains sequence of commands separated by
semicolon, Launchy only runs the first command. Although I have to admit I am
not sure whether such an Exec is not against desktop file specifications, it
looks like other launchers treat this correctly.
Thanks,
Pavel
-- System Information:
Debian Release: stretch/sid
APT prefers testing-proposed-updates
APT policy: (840, 'testing-proposed-updates'), (840, 'testing'), (740,
'unstable'), (738, 'experimental'), (540, 'proposed-updates'), (540, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages launchy depends on:
ii libc6 2.19-20
ii libgcc1 1:5.2.1-17
ii libqt4-network 4:4.8.7+dfsg-3
ii libqtcore4 4:4.8.7+dfsg-3
ii libqtgui4 4:4.8.7+dfsg-3
ii libstdc++6 5.2.1-17
ii libx11-6 2:1.6.3-1
launchy recommends no packages.
Versions of packages launchy suggests:
ii launchy-plugins 2.5-3
ii launchy-skins 2.5-3
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 31 Oct 2015 20:10:54 +0100
Wolfgang <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hello Pavel,
>
> > 1) Having a desktop file with Exec definition pointing to home
> > directory using tilda - e.g. Exec=~/bin/script_name, Launchy is
> > unable to launch the command (simply hitting Enter on the found
> > item from the list does not trigger any action). PS: typing
> > ~/bin/script_name directly in the Launchy window, the script is
> > started. So the problem really seems to be only when combined with
> > a desktop file.
>
>
> > 2) If Exec in a desktop file contains sequence of commands
> > separated by semicolon, Launchy only runs the first command.
> > Although I have to admit I am not sure whether such an Exec is not
> > against desktop file specifications, it looks like other launchers
> > treat this correctly.
>
>
> There is a nice workaround:
> Just use something like :
>
> Exec=sh -c "~/script1"
>
> This will also help you on your second case:
> Exec=sh -c "~/script1; ~/script2"
>
>
> The first feature request seems to be used very seldom so I won't add
> it in my fork. If more people think this would be helpful I can add it
> pretty easy but as there is that workaround it doesn't seem that
> important.
>
> The second feature request is against the desktop specification from
> http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-l
> atest.html#exec-variables
>
> "The Exec key must contain a command line. A command line consists of
> an executable program optionally followed by one or more arguments."
Indeed, closing this bug, and thanks for checking Wolfang!
--
Ricardo Mones
http://people.debian.org/~mones
«Actually, what I'd like is a little toy spaceship!!»
pgpIQojyddNSf.pgp
Description: OpenPGP digital signature
--- End Message ---
