15 Dec
2015
15 Dec
'15
1:19 p.m.
I'm running TDE 14.0.2 on CentOs 6. My compliments to the trinity team
for the excellent job!
I've got back all the reach features of KDE 3, instead of a bloated and
much less usable Plasma thing.
However I've stumbled into an annoying issue.
When clicking on the icon of an executable shell script (extension .sh),
it's opened for editing in Kate, and not launched.
The same, under KDE4 is properly executed.
Is it a matter of some improper setting that I can fix, or a bug?
Additional information.
Looking to the file properties, I see that it's using the settings for
the group "text".
In /opt/trinity/share/mimelink I find both
/text/x-shellscript.desktop
which has a line: X-TDE-IsAlso=application/x-executable-script
and a line [Property::X-TDE-text]
and
/application/x-shellscript.desktop
which has the two identical line, which make little sense IMHO because
if I understand properly they tell that it's also itself, and that it
should be treated as text.
Thanks for any help.
Giuliano
15 Dec
15 Dec
10:37 p.m.
New subject: [trinity-users] cannot launch shell script [Solved]
Il 15/12/2015 14:19, Giuliano Colla ha scritto:
I'm running TDE 14.0.2 on CentOs 6. My compliments
to the trinity team
for the excellent job!
I've got back all the reach features of KDE 3, instead of a bloated
and much less usable Plasma thing.
However I've stumbled into an annoying issue.
When clicking on the icon of an executable shell script (extension
.sh), it's opened for editing in Kate, and not launched.
The same, under KDE4 is properly executed.
Is it a matter of some improper setting that I can fix, or a bug?
Additional information.
Looking to the file properties, I see that it's using the settings for
the group "text".
In /opt/trinity/share/mimelink I find both
/text/x-shellscript.desktop
which has a line: X-TDE-IsAlso=application/x-executable-script
and a line [Property::X-TDE-text]
and
/application/x-shellscript.desktop
which has the two identical line, which make little sense IMHO because
if I understand properly they tell that it's also itself, and that it
should be treated as text.
For anyone interested, I've solved the problem!
I have simply removed x-shellscript.desktop from the mimelnk/text
directory, leaving only the one in the mimelnk/applications and now it
works as expected.
That is, if the script is marked as executable, clicking on it it is
executed. If not it is opened in an editor.
Giuliano
Thanks for any help.
Giuliano
16 Dec
16 Dec
4:32 a.m.
New subject: [trinity-users] cannot launch shell script [Solved]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2015/12/15 11:37 PM, Giuliano Colla wrote:
For anyone interested, I've solved the problem!
I have simply removed x-shellscript.desktop from the mimelnk/text directory, leaving only
the one in the
mimelnk/applications and now it works as expected. That is, if the script is marked as
executable, clicking on it
it is executed. If not it is opened in an editor.
Giuliano
Thanks Giuliano,
this is something we probably need to double check. I guess most users would expect (as
default behavior) scripts to
execute if they double click on it, although for security issues I prefer not to have such
functionality on mine
system (yet I never tested it since I usually do most of the work from a console and mc).
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWcOlIAAoJECp1t8qK3tXPDnUQAJjIkwlpK3AXb0AaQaafvHYv
IIHetd9T4DUqJs7mpfr1FKXvsKUp4eqD9SNAs/+MS7ohI5yWvthIGnU9QllI+li7
N25myyUYXQaEgGHM6T297RVR2lif0rawU9wGlsrcsq3k4jyBAImOGT1TwSZw/aVC
OXodjFRFEwnHniqziEtRPqzCN1yXBuf8OkzwSf94sk+C+UYbAy0onWqMiPf7Rh0L
OEqlADcz8+x1++DtBEi1cD2lHcUa0VGXlUDGYg1/KB4WPdAzxkS7/tYhHSADyxWl
Zn4W1rWCKQ8orlJBG+y+Nikiy7vKXLbKTiW4WxU6adlwxem18oA8RMYbyu6vylpY
DmX7e7PL6VHYW5MPtIvffDi5Cx35t0BfAXWS4ws2MVmeoz6mJl8yP+u9aChtWf+W
lbbbAkAcRK0QiWxqqyRMRjT+afRU+pRsOSkaQFlt7eiDAOg//OqjpRP1zjGAPHQy
paspHb0Lzs3G0M8Kan021fBFhcakqHvoRn6Ey35U+PPzfp/KRTmT+8uOgxLqNL2Z
nNk+/Uyzx7W1CiOY3GhpZSvZA1jELe+lOiuhchCAUhjP7/QvqU8ekZZjE8mR07BH
dGMj0FsiYEtkK9g4gpbsveThN5TzyvxnsPEdYrwUp2ZljUN5sYnO4a2Ypq4TqveC
bPdv9qZ9CXH1i7P40LLM
=Z0Mg
-----END PGP SIGNATURE-----
21 Dec
21 Dec
3:35 p.m.
New subject: cannot launch shell script - question
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/15/2015 11:37 PM, Giuliano Colla wrote:
Il 15/12/2015 14:19, Giuliano Colla ha scritto:
Actually it is not necessary to remove the file /text/x-shellscript.desktop. It is
sufficient to remove the entry for
shell scripts in the "text" category in Konqueror's File Associations
settings.
Slavek, currently tdelibs ships with two files for x-shellscript.desktop:
/opt/trinity/share/mimelnk/application/x-shellscript.desktop
/opt/trinity/share/mimelnk/text/x-shellscript.desktop
I think it would be better to associate shell scripts with one only. IMO most of the users
would expect shell scripts
to be executed when clicking on it from Konqueror.
What do you think?
Any opinion from the other users?
Cheers
Michele
I'm running TDE 14.0.2 on CentOs 6. My
compliments to the trinity team for the excellent job! I've got back all
the reach features of KDE 3, instead of a bloated and much less usable Plasma thing.
However I've stumbled into an annoying issue.
When clicking on the icon of an executable shell script (extension .sh), it's opened
for editing in Kate, and
not launched. The same, under KDE4 is properly executed.
Is it a matter of some improper setting that I can fix, or a bug?
Additional information. Looking to the file properties, I see that it's using the
settings for the group "text".
In /opt/trinity/share/mimelink I find both
/text/x-shellscript.desktop
which has a line: X-TDE-IsAlso=application/x-executable-script and a line
[Property::X-TDE-text]
and
/application/x-shellscript.desktop
which has the two identical line, which make little sense IMHO because if I understand
properly they tell that
it's also itself, and that it should be treated as text.
For anyone interested, I've solved the problem!
I have simply removed x-shellscript.desktop from the mimelnk/text directory, leaving only
the one in the
mimelnk/applications and now it works as expected. That is, if the script is marked as
executable, clicking on it
it is executed. If not it is opened in an editor.
Giuliano
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWeBw0AAoJECp1t8qK3tXPERUQAIadnqcTQCG+FU9edTQDMu5p
q4+94V9Al89OUFrOQIGDJz2o70dDsA77DmYnaNhubT8I243TI+NSgy4DXUqWjnLc
5SDoc6oc7Sm0RPLFVHwudXYc1cSEUl0aZQvkYVnmdeRxTIGCKFYC9wYMK5Y6u9hW
5jgAoWkiTMmigKL5f+tDeXshSvIF1bwotmvRknH9ogeSmqOabS62HXdXIws1CEYc
lhxFxGr7tkCWc6T2qqUi1SmcC940CfSAJa59rc9wEChlrdY0xFk4gVNV/be/8qHt
12cVDVHih0NXTnSHbZw709Zh0SHRc3NS4Uctem7IgxihclvguWhWnmegV+eHpeGh
9BB7Gpxskh/AMgiBUjOfX+AkcVWYLo98Cj2Za5uMj8MlRTff8lD/Kz0TTWcgH0oQ
S52Tmw9T0BRC5hFL0nMWOdlSVxkSuwCe4HeCtsiqR5S2ysvBflD6/L95ACERp2R6
lw3X4w+rpbCXN6MQPDcWSJdg94WIHAE/tjtGJcb+PLGg3WhcEhtEvOe1V9/+dUFY
RTwKF5rVgejcFefp8TOnytY5oyjCxNVaa0JyB9LjqDS37zjnpAB4Q6HVp7hHOfLu
7A+YhYvvsO/04bsg/5iM038z+XM7U8q0mahxkjNZHu2jOU4g+0FT0Sl7BeYEnRcR
50fqAy6koe1fzi7PaJe9
=Fg5c
-----END PGP SIGNATURE-----
4:27 p.m.
New subject: [trinity-users] Re: cannot launch shell script - question
On Monday 21 of December 2015 16:35:16 Michele Calgaro wrote:
On 12/15/2015 11:37 PM, Giuliano Colla wrote:
There is a need to act with caution. As I found when examining the problem
KNotify => problem with playing ogg (see bug 2392), there is an important
relationship between mime types obtained by calling libmagic and mime types
defined in TDE. Missing definition in TDE may cause a problem with the
functionality. It is also necessary to keep in mind that different versions
libmagic may return different types - as is application/ogg × audio/ogg.
The ideal solution would be to leave the /opt/trinity/share/mimelnk in favor
of the system /usr/share/mime. But it will require some effort.
Related links:
+ http://trinity-users.pearsoncomputing.net/?0::9572
+ http://bugs.pearsoncomputing.net/show_bug.cgi?id=2392
--
Slávek
Il 15/12/2015 14:19, Giuliano Colla ha scritto:
Actually it is not necessary to remove the file
/text/x-shellscript.desktop. It is sufficient to remove the entry for shell
scripts in the "text" category in Konqueror's File Associations settings.
Slavek, currently tdelibs ships with two files for x-shellscript.desktop:
/opt/trinity/share/mimelnk/application/x-shellscript.desktop
/opt/trinity/share/mimelnk/text/x-shellscript.desktop
I think it would be better to associate shell scripts with one only. IMO
most of the users would expect shell scripts to be executed when clicking
on it from Konqueror.
What do you think?
Any opinion from the other users?
Cheers
Michele
I'm running TDE 14.0.2 on CentOs 6. My
compliments to the trinity team
for the excellent job! I've got back all the reach features of KDE 3,
instead of a bloated and much less usable Plasma thing.
However I've stumbled into an annoying issue.
When clicking on the icon of an executable shell script (extension .sh),
it's opened for editing in Kate, and not launched. The same, under KDE4
is properly executed.
Is it a matter of some improper setting that I can fix, or a bug?
Additional information. Looking to the file properties, I see that it's
using the settings for the group "text".
In /opt/trinity/share/mimelink I find both
/text/x-shellscript.desktop
which has a line: X-TDE-IsAlso=application/x-executable-script and a
line [Property::X-TDE-text]
and
/application/x-shellscript.desktop
which has the two identical line, which make little sense IMHO because
if I understand properly they tell that it's also itself, and that it
should be treated as text.
For anyone interested, I've solved the problem!
I have simply removed x-shellscript.desktop from the mimelnk/text
directory, leaving only the one in the mimelnk/applications and now it
works as expected. That is, if the script is marked as executable,
clicking on it it is executed. If not it is opened in an editor.
Giuliano
5:57 p.m.
New subject: [trinity-users] Re: cannot launch shell script - question
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/21/2015 05:27 PM, Slávek Banko wrote:
I have created bug 2564 for this enhancement, so we don't forget about it.
Cheers
Michele
Slavek,
currently tdelibs ships with two files for x-shellscript.desktop:
> /opt/trinity/share/mimelnk/application/x-shellscript.desktop
> /opt/trinity/share/mimelnk/text/x-shellscript.desktop I think it would be better to
associate shell scripts
> with one only. IMO most of the users would expect shell scripts to be executed when
clicking on it from
> Konqueror. What do you think?
>
> Any opinion from the other users?
>
> Cheers Michele
>
There is a need to act with caution. As I found when examining the problem
KNotify => problem with playing ogg (see
bug 2392), there is an important relationship between mime types obtained by calling
libmagic and mime types
defined in TDE. Missing definition in TDE may cause a problem with the functionality. It
is also necessary to keep
in mind that different versions libmagic may return different types - as is
application/ogg × audio/ogg.
The ideal solution would be to leave the /opt/trinity/share/mimelnk in favor of the
system /usr/share/mime. But it
will require some effort.
Related links: + http://trinity-users.pearsoncomputing.net/?0::9572 +
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2392
-- Slávek -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWeD14AAoJECp1t8qK3tXPQFwQAKVhli7RltkzxW1Exp73o2xV
ZHbVLbDWF1glYrtx8JQZSutI9SLtATTdLBqK6D93nVrt7f7i/InfnzgH0meSnDDY
l3qlOdfXGPmKA+dixpmampMtN9279W8Mz15bkfw/xflh4PD6Jp7JaQbamAsxacdz
atd/XiLDXbKh4nEhfewErDHN/fP5LTxvQ75OsVjTj/1hkIrZIo0f7GwUWDkze8yM
P0IkeAEXilfRbor0EmTw5FPeb84PPy7zLTggQfb0ElDm6lSEFOpqeoGxH6Uw3Vg5
WXG7eiL5+QoNCHzco+bJ9/xl1NXunh1v0BtpUzA/MekYijwlWV1rwGI0K0/HDAX8
gAHcbLNqhWNMUtN3FbWRfiiOqc/cxuskVN+l5+fFCeYFjD/b19AQXxKkfrYknNWT
ibMMlW1r/AfMV5Rt+VkP3fXUYB348+GvdGf4VvsCfqV6swYnuc0rT9w/kfdaZcTK
qqnnaWCjdwwKemRAuQlD83Chb39WCnX2r6IriJ3kuvYqKMQW/EKz/8wTkVa/sYHR
nKlQj6XC3ghSxL/ZO12vjGWkUTduU9XKZbqC0dafy0v7wtlbu4GmsGxt3l05Wc8X
FzHEkp+UYqjCjgskWycDVeKh/HVVmnVJSK/6q/xa8HKPCxEJfQS/M6rZGN8TnVoN
vga26JMcbZFzr4pYT0Mb
=X0sU
-----END PGP SIGNATURE-----
7:39 p.m.
New subject: [trinity-users] Re: cannot launch shell script - question
Il 21/12/2015 18:57, Michele Calgaro ha scritto:
I have created bug 2564 for this enhancement, so we
don't forget about it.
Cheers
Michele
If this can help to sort the issue, the x-shellscript.desktop entry in
the mimelnk/text folder didn't exist in KDE 3, and doesn't exist in KDE
4 either.
This can mean either that in TDE it's been added there for some good
reasons which should be possible to trace back, or that it has been
inadvertently added, and therefore it could be safely removed.
Giuliano
3321
days inactive
3327
days old
6 comments
3 participants
participants (3)
-
Giuliano Colla -
Michele Calgaro -
Slávek Banko