Version: 2.0.8 (using KDE 1.2) OS: MS Windows When double-clicking gpg-encrypted mails no action is taken. manipulating the registry allows to run commands for various file-extensions (e.g. asc, gpg, pgp) but there is no way to decrypt files with Kleopatra.exe. Starting kelopatra with option -d only works one time. When the process "kleopatra.exe" ist already started the command has no effect. At the moment we start a script when double-clicking an ecrypted file. This script first kills kleopatra.exe and then runs the command kleopatra with parameter "-d" but you will aggree that this is just a poor workaround. Reproducible: Didn't try Expected Results: A small interface for UI-server which is started with kleopatra.exe (and a new parameter) which can be used to open an encrypted file. E.g. kleopatra.exe -[parameter] [file] Or a modification of the method behind parameter "-d" which starts kleopatra and, if is is already running just contacts the UI-server
Andre, is there a way to add this behaviour (double-click = encrypt file) by default in Kleopatra?
The described way should work, regardless if it is running or not repeatedly calling kleopatra with -d Should work. It does work on Linux so if this does not work on Windows it's a bug, probably due to the kleowrap handling. Can you test this with kleo from KDE/4.10?
Calling kleopatra repeatedly with command line arguments still did not work on Windows as the command line arguments were lost in the KUniqueapplication code. I've fixed this now. I'm leaving this wish open because adding the "default application for file extension" is not part of the installer. Btw. alternatively you could have used gpg-connect-agent in a batch script to communicate directly with kleopatra over the assuan protocol.
Git commit 72e8afa2f6d96fee42036aeb96bcbf5a78f58824 by Andre Heinecke. Committed on 16/05/2013 at 09:49. Pushed by aheinecke into branch 'gpg4win'. Add Patch to fix second start of kuniqueapplication This change is mostly taken from the pimuniqueapplication in kdepimlibs. The problem is that on Windows we are always in the nofork mode and thus when a new kuniqueapplication is requested and one is already running, we have just tried to bring this window to front. This lost the command line arguments. A +55 -0 portage/kde/kdelibs/Call-newInstance-on-Windows-if-already-running.patch M +3 -1 portage/kde/kdelibs/kdelibs-20110130.py http://commits.kde.org/emerge/72e8afa2f6d96fee42036aeb96bcbf5a78f58824