Benchmark-Perl-Formance-Cargo
view release on metacpan or search on metacpan
share/SpamAssassin/easy_ham/00973.42545038686536033b1032380502ae09 view on Meta::CPAN
List-Subscribe: <https://listman.spamassassin.taint.org/mailman/listinfo/exmh-users>,
<mailto:exmh-users-request@redhat.com?subject=subscribe>
List-Id: Discussion list for EXMH users <exmh-users.spamassassin.taint.org>
List-Unsubscribe: <https://listman.spamassassin.taint.org/mailman/listinfo/exmh-users>,
<mailto:exmh-users-request@redhat.com?subject=unsubscribe>
List-Archive: <https://listman.spamassassin.taint.org/mailman/private/exmh-users/>
Date: Mon, 02 Sep 2002 19:01:49 -0700
2 things - first, the switch parser changed in a subtle way with 8.4 -
byte-code compilation was added, and it is slightly more strict in
its parsing than the original parser. You can only have a comment where
Tcl would expect to find a command. Switch has a "pattern - body"
strucutre, so if you goof and put a comment where it is trying to find
a pattern, both of you will be confused with the results. The
subtlty arises with extra whitespace and newlines. I can't give you
the exact case, but I know exmh had one example that stopped parsing
correctly, and was arguably wrong before.
2nd - I've managed to remain fairly ignoranat of the PGP support in
exmh, so you'll have to dig in yourself or see if someone else on
exmh-users or exmh-workers is having similar problems.
>>>Reg Clemens said:
> > If you haven't already, you should enable the debug log under
> > Hacking Support preferences and look for clues there.
> >
> > >>>Reg Clemens said:
> > > > Hi,
> > > >
> > > > On Sun, 01 Sep 2002 00:05:03 MDT Reg Clemens wrote:
> > > >
> > > > [...]
> > > > > in messages with GnuPG signatures. But punching the line ALWAYS
> > > > > gives
> > > > >
> > > > > Signature made Thu Aug 29 00:27:17 2002 MDT using DSA key I
D BDD
> > F997A
> > > > > Can't check signature: public key not found
> > > > >
> > > > > So, something else is missing.
> > > >
> > > > Yes, the public key of the signature you want to check :-).
> > > >
> > > > Are you really sure that you have the public key of the message's
> > > > signature? If not, try downloading it or try to check a signature fro
m
> > > > which you know you have the public key.
> > > >
> > > >
> > > >
> > >
> > > Ah, sorry for not making that clearer.
> > > But no.
> > > Previously (v1.0.6 of GnuPG) there would be a slight pause at this poin
t whi
> > le
> > > it went out to get the public key from a keyserver.
> > > Now, whether I have the key or NOT, I get the failure message.
> > >
> > > Its as if it cant find gpg to execute it (but I fixed that path), so th
ere
> > > must be something else that I am missing...
> > >
> > >
> > > --
> > > Reg.Clemens
> > > reg@dwf.com
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Exmh-users mailing list
> > > Exmh-users@redhat.com
> > > https://listman.redhat.com/mailman/listinfo/exmh-users
> >
> > --
> > Brent Welch
> > Software Architect, Panasas Inc
> > Pioneering the World's Most Scalable and Agile Storage Network
> > www.panasas.com
> > welch@panasas.com
> >
>
>
> Partial solution.
> And this MAY be related to using tcl/tk 8.4b1, as I had a similar
> problem about a month ago elsewhere in EXMH (which you found).
>
> But first.
> I really feel like something has changed out from under me
> with my making no changes to EXMH. Namely, when I first got
> GPG up and working (for reading signatures) all I did was
> touch the 'Check Signature' button' and it went out and queried
> the keyserver for me.
> Now Im getting a separate box, after the failure to find the
> public key on my keyring, asking me of I want to 'Query keyserver'
>
> I KNOW that I never had to touch a 'Query keyserver' button in
> the past, but there it is now, and I havent touched EXMH. Spooky.
>
> I have been working back and forth between GPG 1.0.6 and 1.0.7
> but its not clear how that could be the problem, as Im now getting
> the 'Query' message when running either...
>
> ---
>
> OK, enough about my confusion.
> The CURRENT problem seems to be a COMMENT in a SWITCH statement
> at line 86 in pgpWWW.tcl. Tcl 8.4b1 doesnt like it and I get your
> popup box. Remove it and no popupbox, but EXMH hangs (sigh).
> So, not a complete solution, but at least a start.
>
> Thanks for the interest.
>
> Reg.Clemens
> reg@dwf.com
--
Brent Welch
( run in 0.758 second using v1.01-cache-2.11-cpan-364913b4093 )