Re: imap/2097: indication of new mail is not correct after pipe
The following reply was made to PR imap/2097; it has been noted by GNATS.
From: Kyle Wheeler <kyle-mutt-dev@xxxxxxxxxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc: Alain Bench <veronatif@xxxxxxx>
Subject: Re: imap/2097: indication of new mail is not correct after pipe
Date: Sun, 2 Oct 2005 12:30:07 -0500
--Clx92ZfkiYIKRjnr
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Saturday, October 1 at 08:45 PM, quoth Alain Bench:
> Hello Kyle, and again thank you for your reports,
:) 'allo Alain.
> > [in] the index, the indicator that says whether the message is still
> > new or not doesn't get refreshed (to indicate that the message is no
> > longer new) until either the screen gets refreshed (by pressing
> > control-L for example) or until the cursor moves off of the message.
>=20
> Which new indicator? The "N" letter? So it's probably more or less
> intended behaviour, though undocumented: See discussion in mutt/1004
> ""New" flag does not disappear right away in pager with
> pager_index_lines > 0" if it applies. In short: Counting and matching
> (coloring) new is immediate, flag N delayed as a reminder of previous
> state. Note this bug was AFAICS never closed, waiting for the feature to
> be documented. But it disappeared from Gnats: You'll have to search it
> in archives.
Ahh, indeed -- in the pager, when pager_index_lines, I expect this. My=20
situation is when you stay in the index and do not view the message with=20
the pager, but pipe the message to something. Because you've accessed it=20
via IMAP (and because imap_peek=3Dno), piping the message somewhere while=
=20
staying in the index causes to message to become read.
Maybe this is also "intended" behavior... but I don't see a purpose to=20
it.
Part of what makes me think that this is not intended behavior is that=20
if I pipe the message by hand, i.e. type in "|urlview.sh" myself, then=20
mutt marks the message as read right away. But if I pipe the message=20
somewhere from within a macro, the message does not get marked as read.
~Kyle
--=20
I created a cron job to remind me of the Alamo.
-- Arun Rodriguez
--Clx92ZfkiYIKRjnr
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFDQBkfBkIOoMqOI14RAlWXAKC5MPULOseXX8o0hMsPWkomDFzYWgCfTOIA
YtfybkPuF/MEB/tvjRQi2Uk=
=EYst
-----END PGP SIGNATURE-----
--Clx92ZfkiYIKRjnr--