> but in Console, i see:
>
> pinentry-qt: invalid option -- p
> pinentry-qt: invalid option -- s
> pinentry-qt: invalid option -- n
> pinentry-qt: invalid option -- _
> pinentry-qt: invalid option -- 0
> pinentry-qt: invalid option -- _
> pinentry-qt: invalid option -- 3
> pinentry-qt: invalid option -- 1
> pinentry-qt: invalid option -- 9
> pinentry-qt: invalid option -- 8
> pinentry-qt: invalid option -- 1
> pinentry-qt: invalid option -- 5
> pinentry-qt: invalid option -- 6
> pinentry-qt: invalid option -- 9
> OK Your orders please
>
> no idea abt _this_ yet.
well, this seems to be a result of the OSX Finder passing the PSN
(process serial number); in the case above, e.g.,
"-psn_0_31981569"
cref: http://www.kernelthread.com/mac/osx/arch_sys.html
to work around THAT, instead of building an OSX bundle with the
'actual' pinentry-qt cp'd into it, i.e.,
cp -f /usr/local/bin/pinentry-qt pinentry-qt.app/Contents/MacOS/pinentry-qt
create, intstead,
pinentry-osx.app/Contents/MacOS/pinentry-osx
where "pinentry-osx" is a launcher script, e.g.,
------------------
#!/bin/sh
/bin/sh -c '/usr/local/bin/pinentry-qt \
--no-global-grab \
--lc-ctype=UTF-8'
------------------
this launcher simply ignores the Finder-passed PSN, and directly
launches the 'orig' autofoo-built pinentry-qt.
now, on dubl-click of the pinentry-osx.app, no more 'odd' error (as
above). but, still 'nothin' happens -- i.e., there's no dialog
launched. just in Console.log, now,
> OK Your orders please
and, nothing more.
progress? hmm ...
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
