From nobody Sat Jan 4 05:29:11 2003 Newsgroups: gnu.emacs.gnus Subject: Replies pick up headers from wrong message Date: 04 Jan 2003 05:29:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 26 I'm using gnus 5.8.8 on XEmacs, but I've had the same behavior with Emacs. I open a message from someone who uses PGP, and hit 'C-C / d' to decrypt it. When I hit 'F' to reply to it, my message gets the subject from the message (or thread) (often a ticked article) just above the one I was replying to in the summary buffer. It also gets a references header based on the above message's message-id, instead of the one I replied to. Yet the text it yanks in and quotes is from the correct message. Basically it appears that upon decrypting a message, the position in the summary buffer moves up a line, while the article buffer stays in place, and a reply draws from both. This tends to be a little confusing for the recipient, when he receives a message from me with a subject that might be months old, commenting on a new topic and quoting his new text. I think I can keep this from happening by decrypting the message, then going to read another message, coming back and re-reading the new message, and then replying. But that's extra trouble, and easy to forget to do. Has anyone else had this problem, or know of a solution? Thanks, -- Aaron From nobody Fri Jan 10 10:48:28 2003 Newsgroups: gnu.emacs.gnus Subject: Re: Replies pick up headers from wrong message Date: 10 Jan 2003 10:48:27 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 16 Lars Magne Ingebrigtsen writes: > Odd. `C-c / d' is a MailCrypt keystroke, I guess? Yes. > Anyway, in Oort Gnus all the PGP stuff has been redone, so I'm > guessing this bug no longer applies to Oort. I've been meaning to move to Oort; I guess it's time. Thanks, -- Aaron From nobody Tue Jan 14 17:07:52 2003 Newsgroups: gnu.emacs.gnus Subject: Can I customize hidden thread indicator? Organization: ESC Date: 14 Jan 2003 17:07:51 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 18 I have gnus-summary-hide-thread set to t, so threads are hidden until I select them. To indicate a hidden thread, gnus adds three dots to the end of the summary line, like this: [100: Aaron Baugher ] This is a test ... On my screen, those dots are hard to see. Also, authors occasionally put multiple dots at the end of their subject lines, making them look like hidden threads. Is it possible to get gnus to use something else to indicate a hidden thread, like "==="? It doesn't appear to be part of gnus-summary-line-format, and I can't find anything about it in the info for gnus. Thanks, -- Aaron From nobody Wed Jan 15 06:21:25 2003 Newsgroups: gnu.emacs.gnus Subject: Re: Can I customize hidden thread indicator? Organization: ESC Date: 15 Jan 2003 06:21:24 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Lines: 18 kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes: > > On my screen, those dots are hard to see. Also, authors > > occasionally put multiple dots at the end of their subject lines, > > making them look like hidden threads. Is it possible to get gnus > > to use something else to indicate a hidden thread, like "==="? > See the %t and %e specifiers for gnus-summary-line-format. Thanks. That won't get rid of the "...", but I think it'll accomplish what I'm looking for. -- Aaron From nobody Thu Jan 16 16:37:43 2003 Newsgroups: gnu.emacs.gnus Subject: Re: Can I customize hidden thread indicator? Organization: ESC Date: 16 Jan 2003 16:37:42 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Lines: 15 bojohan@helm.dd.chalmers.se (Johan Bockgård) writes: > kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes: > > I wonder if the variable selective-display-ellipses can disable > > those? It would be surprising in a way, but logical in another > > way. > Tried it. It does. Thanks! -- Aaron From nobody Mon Nov 22 17:32:42 2004 Newsgroups: gnu.emacs.gnus Subject: pgg-parse-crc24 error Organization: ESC Date: Mon, 22 Nov 2004 17:32:40 -0600 Message-ID: <861xel7947.fsf@cail.baugher.pike.il.us> berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 23 I recently switched from XEmacs to XEmacs-mule (21.4-p14) on FreeBSD, using the ports tree, and now I can't encrypt or decrypt in gnus. When I try, I get this error: Symbol's value as variable is void: pgg-parse-crc24 Here's the relevant portion from my .gnus: (setq pgg-cache-passphrase t pgg-passphrase-cache-expiry 60000 pgg-encrypt-for-me t mm-decrypt-option "known" gnus-message-replyencrypt t mml-default-encrypt-method "pgpmime" ) Any suggestions? Thanks, -- From nobody Tue Nov 23 05:40:09 2004 Newsgroups: gnu.emacs.gnus Subject: Re: pgg-parse-crc24 error References: <861xel7947.fsf@cail.baugher.pike.il.us> <86hdnhxx2h.fsf@santinel.home.ua> Organization: ESC Date: Tue, 23 Nov 2004 05:40:09 -0600 Message-ID: <86y8gs4wva.fsf@cail.baugher.pike.il.us> berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 21 Andrey Slusar writes: >> Symbol's value as variable is void: pgg-parse-crc24 > package pgg is installed? Looks that way: /usr/local/lib/xemacs/site-packages/lisp/gnus/pgg.el /usr/local/lib/xemacs/site-packages/lisp/gnus/pgg.elc But, when I add this line to my .gnus: (require 'pgg) Then I get the error as soon as I try to reload .gnus. Thanks, -- From nobody Wed Nov 24 07:38:55 2004 Newsgroups: gnu.emacs.gnus Subject: Re: pgg-parse-crc24 error References: <861xel7947.fsf@cail.baugher.pike.il.us> <86hdnhxx2h.fsf@santinel.home.ua> <86y8gs4wva.fsf@cail.baugher.pike.il.us> Organization: ESC Date: Wed, 24 Nov 2004 07:38:52 -0600 Message-ID: <86d5y3z7rn.fsf@cail.baugher.pike.il.us> berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 15 Michael Slass writes: > What does > M-x locate-library RET ppg RET > show you? Thanks, that helped me find the problem. I had an old copy of gnus in another directory, and it was picking up the pgg.elc from there first. I deleted that, and everything is working now. I'll have to remember that locate-library command. Thanks again, --