
On 09/19/2017 07:21 AM, Bjoern Voigt wrote: own executable file unless it has the executable bit.
BTW, my Ark currently uses the following settings in "General Settings":
[x] Preview the file with internal previewer [ ] Open the file with associated application [x] Show a warning when creating zip archives with AES encryption
So, with these settings Ark must not open a VBS script with the associated application (Wine + Microsoft Office).
I probably should file a bug. Currently Ark has 47 confirmed and unconfirmed open bugs: https://bugs.kde.org/buglist.cgi?component=general&list_id=1465085&product=a...
I suspect the problem is that first checkbox, - Preview the file. It should probably launch what ever would be used to edit that file, but instead hands it off to wine. This is still handled by your DE, (KDE in my case) under System settings/ Applications / File Associations / under the treeview of known associations applications / x-wine-extensions (the latter most of these). That says to launch "wine start" wine start operates by inspection of the extension. Given no file, "wine start" simply starts a dos box. You might be able to add an editor to that list as the first most option, most wine installs include wordpad as a default. or remove that entry all together so that nothing is done with a .vbs file. It seems like this issue lies halfway between kde (or any other DE) and wine. ARK simply hands it off to KDE, KDE checks its list of applications and hands it off to wine. Wine does that ever windows would do. Still your problem is expecting the system to handle your errant click intelligently, and apply Linux permissions onto a Windows system. I think that's beyond scope of wine. But I don't know this for sure. Wine is a strange animal, best avoided imho. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org