Gnus development mailing list
 help / color / mirror / Atom feed
From: Manuel Carro <mcarro@fi.upm.es>
To: ding@gnus.org
Subject: Re: Show mark in unread emails
Date: Wed, 21 Dec 2011 16:35:50 +0100	[thread overview]
Message-ID: <7sobv2j5t5.fsf@fi.upm.es> (raw)
In-Reply-To: <87hb0vrnjp.fsf@topper.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Tue, 20 Dec 2011 21:33:14 +0100")


> > I tried it.
> 
> I didn't see you reporting that it didn't work, before?

You are right, I didn't.  I was not sure group parameters were the way
to go (I had never used them before) and so I thought I could try
something different, started playing with the different marking options,
and eventually send the initial message.

> > So, yes, I tried to follow that path, but unsuccessfuly so far.
> 
> If you had said from the beginning that that was what you wanted to
> achieve, but couldn't make work, it would have saved us all a lot of
> time :-)

Well, I tried to explain what I was after, but as I said I didn't see
solving the group parameters issue as the key.  Now I see (thanks
everyone) that it can be a way to achieve what I am after.  So I
apologize for the waste of everyone's time, perhaps especially to
Philipp Haselwarter who had pointed me to the right info page but which
I overlooked.

> Nope, when I use exactly what he wrote - i.e. I use G p on a group:
> [...]

Yes, writing it like that does not make Gnus complain after C-cC-c.
However I am afraid I am finding a difficulty: I do mark some messages
as expirable (so that the messages are marked with `E'), and I cannot
find a group parameter expression which shows unseen messages, read
messages, and ancient messages but not messages marked as expirable.  It
seems to me that the 'expire' operator of the group parameters selects
messages which are not expirable because they are younger than the
time-to-expire parameter for the group.  Do anyone of you have any idea
of how I can make marked-to-expire messages not to show up in the
summary?

Cheers and thanks again!



  reply	other threads:[~2011-12-21 15:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 12:44 Show read emails? Petro
2011-12-16 16:59 ` Steinar Bang
2011-12-16 19:58   ` Wes Hardaker
2011-12-17 10:46   ` Vitalie Spinu
2011-12-17 11:03     ` Adam Sjøgren
2011-12-17 21:25       ` Steinar Bang
2011-12-18 23:08 ` Show mark in unread emails Manuel Carro
2011-12-19  0:15   ` Russ Allbery
2011-12-19  1:25     ` Manuel Carro
2011-12-19 14:20       ` Adam Sjøgren
2011-12-20  8:09         ` Manuel Carro
2011-12-20 11:23           ` Philipp Haselwarter
2011-12-20 18:33             ` Manuel Carro
2011-12-20 18:56               ` Adam Sjøgren
2011-12-20 19:16                 ` Manuel Carro
2011-12-20 20:14                   ` Adam Sjøgren
2011-12-20 20:24                     ` Manuel Carro
2011-12-20 20:33                       ` Adam Sjøgren
2011-12-21 15:35                         ` Manuel Carro [this message]
2011-12-20 20:18                   ` Philipp Haselwarter
2011-12-20 20:31               ` Philipp Haselwarter
2011-12-19  1:57     ` XeCycle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7sobv2j5t5.fsf@fi.upm.es \
    --to=mcarro@fi.upm.es \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).