--nextPart2383672.BuIHA8jaXX
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

 as we all know, *nix file system store a property about each file: is=20
it executable or not. If it is not, it won't be executed, even if the=20
content is executable. The extension, luckily, does not matter.
 In the GUI (KDE) you start executables by clicking on them. That's=20
fine, until...you have an executable for what there is an associated=20
application. For example, you associated Kate to .sh files, or more=20
common, you associated a Python editor to .py files.
In that case KDE ignores the executable bit and happily opens the file=20
in whatever application it is specified.=20
Short example, which does not require system changes. Create a test.txt =20
file with this content:
#!/bin/bash
kdialog --msgbox "I am a GUI application!"

Make this executable (chmod +x test.txt) and click on it in=20
Konqueror/Dolphin.=20
The file is not executed, it is opened in your default editor.

I checked and as far as I saw, for some mimetypes, like x-shellscript,=20
this is workaround by inheriting from x-executable-script (a KDE hack in=20
KDE3, which seems to be adopted by freedesktop).

My simple question is why does not honor KDE the executable bit,=20
indifferently of what the mimetype description says? The above test.txt=20
is no different from the same file called test.sh.=20
Think also of php files (the mimetype does not inherit from x-
executable, but you can have php applications without a web server), or=20
other script files.

I know there is a solution by changing the mimetype description, still=20
I'd like to hear the reason of this behavior (and possibly what others=20
think about).

Andras

=2D-=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org


--nextPart2383672.BuIHA8jaXX
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHm58RTQdfac6L/08RApwHAKDRkdR8uT0s8r0k5XRQef3ZYsN94wCfbttQ
yvd+esC65f920g6LuvM2Xsc=
=skxh
-----END PGP SIGNATURE-----

--nextPart2383672.BuIHA8jaXX--