headers
Nevin Kapur | 1 Oct 2001 02:11
X-Face
Favicon

Re: limit to recipient?

Amos Gouaux <amos+lists.ding <at> utdallas.edu> writes:

> Here's why: when I go into my sent-mail folders, I would like to be
> able to narrow on messages I sent to a particular recipient.  Any
> way to do that?

If you have To as a gnus-extra-header then you can use '/ x' to narrow
to recipients.

--

-- 
Nevin Kapur
nevin <at> jhu.edu
Permalink | Reply | 0 comments |
headers
Lloyd Zusman | 1 Oct 2001 02:35
X-Face

Changed criteria for deciding if articles have been read?

I've been away from the group for a month or so, and I haven't done a
CVS update in that long.

I just now did the CVS update, and when I run the resultant gnus
build, I see many old articles in almost all my groups showing up as
unread.

The weird thing about this is that not all old articles show up as
unread ... only maybe the past 3-5 weeks' worth.

If I switch to my older version of Oort, the unread-ness of the
articles once again appears correct.

Are recent Oort versions doing something different with marks, or
something?

Forgive me if this has been discussed during the past few weeks, but
due to my absence, I've gotten way behind in all my mailing list and
newsgroup reading, and I still haven't been able to catch up on
everything I've missed.

Feel free to email me privately if this has recently been discussed
and you don't want to clutter the group with redundant info.

Thanks in advance.

--

-- 
 Lloyd Zusman
 ljz <at> asfast.com
(Continue reading)

Permalink | Reply | 9 comments |
headers
Lloyd Zusman | 1 Oct 2001 03:31
X-Face

I lied (Was: Group-specific gnus-auto-select-next?)

Lloyd Zusman <ljz <at> asfast.com> writes:

> [ ... ]
>
> Kai.Grossjohann <at> CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>> Lloyd Zusman <ljz <at> asfast.com> writes:
>> 
>>> Here it is:
>>>
>>>  ;; Wrap `gnus-summary-read-group' so that `gnus-auto-select-next'
>>>  ;; gets set according to `no-auto-select-pattern'
>>>
>>>  (defadvice gnus-summary-read-group (around gnus-summary-read-group freeze)
>>>    [ ... etc. ... ]
>>>
>>> I did this because it seemed at the time that there was no other way
>>> to selectively set `gnus-auto-select-next' based upon the name of the
>>> newsgroup.  [ ... ]
>> 
>> Hm.  Does it work to set a local variable in the group parameters?
>> 
>> (setq gnus-parameters '(("e" (gnus-auto-select-next t))
>>                         (""  (gnus-auto-select-next nil))))
>> 
>> Maybe this sets it to t for all group names with e in them.
> 
> I tried this, and indeed it works.
> 
> Thank you very much.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jorge Godoy | 1 Oct 2001 07:02
Favicon

[OT?] GPG encryption to self


Hi!

How does one configure Gnus to encrypt to self together with
encrypting a message to the recipient? I can encrypt a message, but
then I can't read the sent message later.

I use gpg.el...

--

-- 
Godoy. <godoy <at> conectiva.com>

Solutions Developer       - Conectiva Inc. - http://en.conectiva.com
Desenvolvedor de Soluções - Conectiva S.A. - http://www.conectiva.com.br
Permalink | Reply | 2 comments |
headers
Jorge Godoy | 1 Oct 2001 07:06
Favicon

Re: Fun with article highlighting

Simon Josefsson <jas <at> extundo.com> writes:

> [[[[PPGGPP  SSiiggnneedd  PPaarrtt::OOKK]]]]
>
> So, is this message properly signed or not?

As you can see by the strings you've putten above, you haven't even
signed it. :-)

This is nice to know that Gnus (gpg.el? mailcrypt?) actually puts your
fingerprint for keys you haven't signed and/or puts the user name for
signed keys. It is also nice to _always_ expand the "GPG Signed: OK"
message to be sure. ;-)

This shows that one cannot always trust in what he sees. :-)

> (Some out-of-band mechanism to signal security status would be nice,
> such as arrows in the fringe.  O well.)

??? I didn't understand it.

--

-- 
Godoy. <godoy <at> conectiva.com>

Solutions Developer       - Conectiva Inc. - http://en.conectiva.com
Desenvolvedor de Soluções - Conectiva S.A. - http://www.conectiva.com.br
Permalink | Reply | 1 comment |
headers
Christoph Conrad | 1 Oct 2001 08:09
Picon
Picon

Re: Changed criteria for deciding if articles have been read?

    > Are recent Oort versions doing something different with marks,
    > or something?

(setq nnml-marks-is-evil     t
      nnfolder-marks-is-evil t)
Permalink | Reply | 0 comments |
headers
Ulf Stegemann | 1 Oct 2001 09:56
Picon
Favicon

Re: [OT?] GPG encryption to self

Jorge Godoy <godoy <at> conectiva.com> wrote:

> How does one configure Gnus to encrypt to self together with
> encrypting a message to the recipient? I can encrypt a message, but
> then I can't read the sent message later.
> 
> I use gpg.el...

Did you set the following?

(setq mc-encrypt-for-me t) 

Ulf

--

-- 
Yes, you can use Outlook ... as long as you know it's wrong.
Permalink | Reply | 1 comment |
headers
Didier Verna | 1 Oct 2001 10:07
X-Face
Picon
Picon
Favicon
Gravatar

Re: New mail appears to be old?!

"Georg C. F. Greve" <greve <at> gnu.org> wrote:

> The CVS version of nndiary I'm getting in the gnus/lisp directory
> claims to be ";; Last Revision: Wed Aug  8 17:36:21 2001" which seems
> rather old for something so new. Is this as it ought to be?

        Don't worry about that. It's an artefact of a package of mine that I
use to maintain file contents, but now that nndiary is in CVS and might be
touched by the other gnus developers, I'll probably remove this header.

--

-- 
Didier Verna, didier <at> lrde.epita.fr, http://www.lrde.epita.fr/~didier

EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 44 08 01 99   didier <at> xemacs.org
Permalink | Reply | 0 comments |
headers
Kai Großjohann | 1 Oct 2001 11:39
Picon
Picon

Re: I lied (Was: Group-specific gnus-auto-select-next?)

Lloyd Zusman <ljz <at> asfast.com> writes:

> What follows at the end of this message is the code for
> `gnus-summary-read-group'.  Notice the 10th line of that function,
> where `gnus-auto-select-next' is set to nil in the `let' block.  This
> causes any and all changes to the value of `gnus-auto-select-next'
> from within `gnus-summary-read-group-1' to get undone after that
> function returns.

This seems to be a bad thing, and IWBNI some other way could be
devised to achieve the same effect.

Why is gnus-auto-select-next bound to nil, anyway?

Thanks for being willing to work on this.

kai
--

-- 
Abort this operation?   [OK]  [Cancel]
Permalink | Reply | 1 comment |
headers
Lloyd Zusman | 1 Oct 2001 12:27
X-Face

Re: I lied (Was: Group-specific gnus-auto-select-next?)

Kai.Grossjohann <at> CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Lloyd Zusman <ljz <at> asfast.com> writes:
> 
>> What follows at the end of this message is the code for
>> `gnus-summary-read-group'.  Notice the 10th line of that function,
>> where `gnus-auto-select-next' is set to nil in the `let' block.  This
>> causes any and all changes to the value of `gnus-auto-select-next'
>> from within `gnus-summary-read-group-1' to get undone after that
>> function returns.
> 
> This seems to be a bad thing, and IWBNI some other way could be
> devised to achieve the same effect.
> 
> Why is gnus-auto-select-next bound to nil, anyway?

I'm going to make a wild guess as to why: perhaps it's set to nil to
avoid problems if the group being read by `gnus-summary-read-group' is
empty at the time that function is being invoked.

But whatever the case, I agree with you that there probably would be
other ways to achieve the intended effect of the temporary binding of
`gnus-auto-select-next' to nil, whatever that intended effect might
be.

> Thanks for being willing to work on this.

Tonight or tomorrow I'll experiment with this routine, to see if I can
determine the intention of binding `gnus-auto-select-next' to nil, and
if so, then to see if I can devise a different way to achieve this
(Continue reading)

Permalink | Reply | 0 comments |

Gmane