Topics : total unread

Topics : total unread

[Richard G Riley]

I have my gnus structured into different topics one of which is email.

How can I stop my "nnfolder+archive:.mail.2008-03" contributing to the
"unread" total show in the topic header? This is just an archive of sent
messages. I suppose one way is to simply mark all articles saved there
as read. What would be the most efficient way to do this?

Re: Topics : total unread

[Adam Sjøgren]

On Sat, 22 Mar 2008 15:31:16 +0100, Richard wrote:

> How can I stop my "nnfolder+archive:.mail.2008-03" contributing to the
> "unread" total show in the topic header? This is just an archive of sent
> messages. I suppose one way is to simply mark all articles saved there
> as read. What would be the most efficient way to do this?

I use this to have my archived (gcc'ed) mail marked as read
automatically:

 ; New Gnus-function: mark gcc'ed as read - coool!:
 (setq gnus-inews-mark-gcc-as-read t)


  Best regards,

-- 
 "You know, if the sun was an oboe, what would you do?"       Adam Sjøgren
                                                         asjo@koldfront.dk

Re: Topics : total unread

[Bastien]

asjo@koldfront.dk (Adam Sjøgren) writes:

>  ; New Gnus-function: mark gcc'ed as read - coool!:
>  (setq gnus-inews-mark-gcc-as-read t)

I don't know about this variable, where does it come from?

I use this:

  (setq gnus-gcc-mark-as-read t)

-- 
Bastien

Re: Topics : total unread

[Adam Sjøgren]

On Sat, 22 Mar 2008 16:59:32 +0100, Bastien wrote:

> asjo@koldfront.dk (Adam Sjøgren) writes:

>> (setq gnus-inews-mark-gcc-as-read t)

> I don't know about this variable, where does it come from?

> I use this:

>   (setq gnus-gcc-mark-as-read t)

Looks like a better named one; yes, you are right:

,----[ C-h v gnus-inews-mark-gcc-as-read RET ]
| `gnus-inews-mark-gcc-as-read' is a variable declared in Lisp.
| 
| Value: t
| 
| Documentation:
| Obsolete; use `gnus-gcc-mark-as-read' instead.
| 
| not documented as a variable.
`----

(it is from gnus-msg.el).

My .gnus has been built over a while, so a bunch of stuff is obsolete... 
Thanks for the tip!


  Best regards,

-- 
 "You know, if the sun was an oboe, what would you do?"       Adam Sjøgren
                                                         asjo@koldfront.dk

Re: Topics : total unread

[Reiner Steib]

On Sat, Mar 22 2008, Bastien wrote:

> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>>  ; New Gnus-function: mark gcc'ed as read - coool!:
>>  (setq gnus-inews-mark-gcc-as-read t)
>
> I don't know about this variable, where does it come from?

,----[ <f1> v gnus-inews-mark-gcc-as-read RET ]
| gnus-inews-mark-gcc-as-read's value is t
| 
| This variable is obsolete;
| use `gnus-gcc-mark-as-read' instead.
`----

> I use this:
>
>   (setq gnus-gcc-mark-as-read t)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Topics : total unread

[Sébastien Vauban]

Hi,

>> ; New Gnus-function: mark gcc'ed as read - coool!:
>  (setq gnus-gcc-mark-as-read t)

Following your advice (on this newsgroup, a couple of weeks
ago), I did give a try to this, but stopped after it appeared
really slooow to update the marks.

At least, it really takes ages for the mark updates in the
groups containing a lot of mail. In particular, I'm talking of
my main mailbox which contains 17.000 mails or so.

Using the above, I had to wait for around one minute to get back
to the summary buffer...

I'm thus back to the old way: manually marking every sent item
as read.

Sebastien

-- 
Sébastien Vauban

Re: Topics : total unread

[Adam Sjøgren]

On Tue, 25 Mar 2008 14:56:08 +0100, Sébastien wrote:

>>> ; New Gnus-function: mark gcc'ed as read - coool!:
>> (setq gnus-gcc-mark-as-read t)

> Following your advice (on this newsgroup, a couple of weeks
> ago), I did give a try to this, but stopped after it appeared
> really slooow to update the marks.

That sounds weird to me. But then again, my archive groups are per year
and I don't write tens of thousands of mail/news per year ;-)

> At least, it really takes ages for the mark updates in the
> groups containing a lot of mail. In particular, I'm talking of
> my main mailbox which contains 17.000 mails or so.

Are you gcc'ing to the same group or another group for archival?


  Best regards,

-- 
 "Anyone for cricket?"                                        Adam Sjøgren
                                                         asjo@koldfront.dk

Re: Topics : total unread

[Sébastien Vauban]

Hi Adam,

>>> ;; New Gnus-function: mark gcc'ed as read - coool!
>>> (setq gnus-gcc-mark-as-read t)
>>
>> I did give a try to this, but stopped after it appeared
>> really slooow to update the marks.
>
> That sounds weird to me. But then again, my archive groups are
> per year and I don't write tens of thousands of mail/news per
> year ;-)

I don't either ;-)


>> At least, it really takes ages for the mark updates in the
>> groups containing a lot of mail. In particular, I'm talking
>> of my main mailbox which contains 17.000 mails or so.
>
> Are you gcc'ing to the same group or another group for
> archival?

The group I'm talking of is the one which contains all the
*received and sent* mails from/to my colleagues, over the
4 years and a half I'm using Gnus.

So, yes:

    o   I apply automatic splitting to my incoming mails, so
        that it gets sorted by (groups of) emitters: family,
        friends, colleagues, ...

    o   and I always GCc to the corresponding group - when
        answering -, so that the threading of my conversations
        works nicely.

This explains that, in particular, my "work" group is getting
big, with ~ 17.000 mails.

Applying the above described method for automatically marking my
answers as read mails is incredibly slow for that one group (one
minute, or more); though, it was OK for smaller groups.

Best regards,
  Seb

-- 
Sébastien Vauban