Mark message inconditionnaly as read.

I do not thind a function in index mode which would mark a message as
read, wether or not it is marked as new. N(toggle-read) will mark a new
message as read, but will also mark a read message as new, which I do
not want.

Is there a solution ?

--
Erwan

* Erwan David (2007-06-14):
>
>
> I do not thind a function in index mode which would mark a message as
> read, wether or not it is marked as new. N(toggle-read) will mark a new
> message as read, but will also mark a read message as new, which I do
> not want.
>
> Is there a solution ?

<untag-pattern>~A<enter><tag-pattern>~N<enter><clear-flag>N<untag-pattern>~A<enter>

-André

--
May as well be hung for a sheep as a lamb!
Linux Kernel 2.6/PPC for Linkstation/KuroBox/HG/HS from http://hvkls.dyndns.org

* André Berger (2007-06-14):
> * Erwan David (2007-06-14):
> >
> >
> > I do not thind a function in index mode which would mark a message as
> > read, wether or not it is marked as new. N(toggle-read) will mark a new
> > message as read, but will also mark a read message as new, which I do
> > not want.
> >
> > Is there a solution ?
>
> <untag-pattern>~A<enter><tag-pattern>~N<enter><clear-flag>N<untag-pattern>~A<enter>

That's for all messages of course, you asked for <clear-flag>N

-André

--
May as well be hung for a sheep as a lamb!
Linux Kernel 2.6/PPC for Linkstation/KuroBox/HG/HS from http://hvkls.dyndns.org

André Berger <andre.berger@web.de> disait le 06/14/07 que :

> * Erwan David (2007-06-14):
>>
>>
>> I do not thind a function in index mode which would mark a message as
>> read, wether or not it is marked as new. N(toggle-read) will mark a new
>> message as read, but will also mark a read message as new, which I do
>> not want.
>>
>> Is there a solution ?
>
> <untag-pattern>~A<enter><tag-pattern>~N<enter><clear-flag>N<untag-pattern>~A<enter>
>

Thank you. I wanted it just for one particular message (the one seen by
my macro) and had missed the "clear-flag" function.

--
Erwan

André Berger <andre.berger@web.de> disait le 06/14/07 que :

> * Erwan David (2007-06-14):
>>
>>
>> I do not thind a function in index mode which would mark a message as
>> read, wether or not it is marked as new. N(toggle-read) will mark a new
>> message as read, but will also mark a read message as new, which I do
>> not want.
>>
>> Is there a solution ?
>
> <untag-pattern>~A<enter><tag-pattern>~N<enter><clear-flag>N<untag-pattern>~A<enter>
>

Thank you. I wanted it just for one particular message (the one seen by
my macro) and had missed the "clear-flag" function.

However, using <clear-flag>N changes to next message, breaking my macro
(which is <clear-flag>N<save-message>=spam\n\n)
Thus the wrong message is saved to the spam folder (used to
train the bayesian filter).

I fear that if next message is marked as "deleted" using
<previous-entry> before <save-message> won't work

--
Erwan

Erwan David wrote:
> However, using <clear-flag>N changes to next message, breaking my macro
> (which is <clear-flag>N<save-message>=spam\n\n)
> Thus the wrong message is saved to the spam folder (used to
> train the bayesian filter).

One option could simply be to mark all e-mails in the spam folder as
read on entry, and (if using maildir) make the training program look in
spam/new as well as spam/cur.

Hope this helps,

James.

--
E-mail: james@ | "The Aldis lamp was developed to flash Morse Code
aprilcottage.co.uk | instructions between ships, with the result that one
| foggy night in December, a British destroyer found itself
| taking orders from the Bismarck's Christmas disco lights,
| and set off to attack the YMCA." -- "ISIHAC", BBC R4

* Erwan David (2007-06-14):
> André Berger <andre.berger@web.de> disait le 06/14/07 que :
> > * Erwan David (2007-06-14):
> >>
> >> I do not thind a function in index mode which would mark a message as
> >> read, wether or not it is marked as new. N(toggle-read) will mark a new
> >> message as read, but will also mark a read message as new, which I do
> >> not want.
> >
> > <untag-pattern>~A<enter><tag-pattern>~N<enter><clear-flag>N<untag-pattern>~A<enter>
>
> Thank you. I wanted it just for one particular message (the one seen by
> my macro) and had missed the "clear-flag" function.

<clear-flag>N

> However, using <clear-flag>N changes to next message, breaking my macro
> (which is <clear-flag>N<save-message>=spam\n\n)
> Thus the wrong message is saved to the spam folder (used to
> train the bayesian filter).

set reverse=no

-André

James Wilkinson <see-sig@aprilcottage.co.uk.invalid> disait le 06/14/07 que :

> Erwan David wrote:
>> However, using <clear-flag>N changes to next message, breaking my macro
>> (which is <clear-flag>N<save-message>=spam\n\n)
>> Thus the wrong message is saved to the spam folder (used to
>> train the bayesian filter).
>
> One option could simply be to mark all e-mails in the spam folder as
> read on entry, and (if using maildir) make the training program look in
> spam/new as well as spam/cur.
>
> Hope this helps,

The problem is more complicated : the backend is imap as I also have to
read my mail from a windows with thunderbird. On thunderbird the spam
folder must be selected.
I use imap_check_subscribed to see the new mail in the subscribed
folders, but I'd prefer that mutt does not send me to the spam folder
to see the spam I've just put here. Thus my tries to mark the message as
read in the macro.

The other solutuion is to get the list of subecribed folers, remove spam
from it and stop using imap_check_subscribed.

--
Erwan

* André Berger on Friday, June 15, 2007:
> * Erwan David (2007-06-14):
>> However, using <clear-flag>N changes to next message, breaking my macro
>> (which is <clear-flag>N<save-message>=spam\n\n)
>> Thus the wrong message is saved to the spam folder (used to
>> train the bayesian filter).
>
> set reverse=no

Shouldn't that be "set resolve=no" ?

c
--
Python Mutt utilities <http://www.blacktrash.org/hg/muttils/>

Christian Ebert <blacktrash@gmx.net> disait le 06/15/07 que :

> * André Berger on Friday, June 15, 2007:
>> * Erwan David (2007-06-14):
>>> However, using <clear-flag>N changes to next message, breaking my macro
>>> (which is <clear-flag>N<save-message>=spam\n\n)
>>> Thus the wrong message is saved to the spam folder (used to
>>> train the bayesian filter).
>>
>> set reverse=no
>
> Shouldn't that be "set resolve=no" ?
>

Thanks, One more thing I had missed.

But now my macro
macro index "<Esc>j" "<enter-command>set resolve=no\n<clear-flag>N<save-message>=spam\n\n<enter-command>set resolve=yes\n"

is not accepted by mutt : too many arguments. This I do not see where it
can come from...

--
Erwan