Lloyd Zusman | 2 Jul 2006 02:41

Re: Hiding messages that are already read?

Hi again ... I'm repeating my question by quoting my own message,
because this message doesn't appear to have been propagated.

Thanks.

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

> Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:
>
>> At Tue, 27 Jun 2006 06:49:35 -0400,
>> Lloyd Zusman wrote:
>>> 
>>> [ ... ]
>>>
>>> Is there truly no way to do this?  The ability to hide already-read
>>> messages when I enter a group is just about the only feature of Gnus
>>> that might keep me from switching to Wanderlust.
>>
>> Use filter folder with condition "flag:any".
>
> Thank you very much.
>
> So, if I am using filter folders, how do I make the original folders
> that they are referencing invisible?  I'm asking this because I would
> want "flag:any" on all my folders, without exception, and I will not
> want to see the original (non-filtered) folders at all.

--

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

Yoichi NAKAYAMA | 2 Jul 2006 04:44
X-Face
Gravatar

Re: Hiding messages that are already read?

At Tue, 27 Jun 2006 17:10:56 -0400,
Lloyd Zusman wrote:
> 
> Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:
> 
> > At Tue, 27 Jun 2006 06:49:35 -0400,
> > Lloyd Zusman wrote:
> >> 
> >> [ ... ]
> >>
> >> Is there truly no way to do this?  The ability to hide already-read
> >> messages when I enter a group is just about the only feature of Gnus
> >> that might keep me from switching to Wanderlust.
> >
> > Use filter folder with condition "flag:any".
> 
> Thank you very much.
> 
> So, if I am using filter folders, how do I make the original folders
> that they are referencing invisible?  I'm asking this because I would
> want "flag:any" on all my folders, without exception, and I will not
> want to see the original (non-filtered) folders at all.

How about having filtered ones in your folder list (~/.folders),
instead of non-filtered ones?
--

-- 
Yoichi NAKAYAMA

Lloyd Zusman | 2 Jul 2006 05:10

Re: Hiding messages that are already read?

Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:

> At Tue, 27 Jun 2006 17:10:56 -0400,
> Lloyd Zusman wrote:
>> 
>> Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:
>> >
>> > [ ... ]
>> >
>> > Use filter folder with condition "flag:any".
>> 
>> Thank you very much.
>> 
>> So, if I am using filter folders, how do I make the original folders
>> that they are referencing invisible?  I'm asking this because I would
>> want "flag:any" on all my folders, without exception, and I will not
>> want to see the original (non-filtered) folders at all.
>
> How about having filtered ones in your folder list (~/.folders),
> instead of non-filtered ones?

Well, when I asked my question, I was confused.  I incorrectly thought
that both sets of folders (filtered and non-filtered) had to be in my
~/.folders file in order for the filtering to work.  But after reading
your reply, I re-checked the documentation and realized my error.

Now I see that I can indeed have only the filtered folders in my
~/.folders file.  Thank you for helping me understand this.

--

-- 
(Continue reading)

Lloyd Zusman | 2 Jul 2006 05:20

Re: Hiding messages that are already read?

bremner <at> unb.ca writes:

>>>>>> "Yoichi" == Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:
>
>
>     Yoichi> At Tue, 27 Jun 2006 06:49:35 -0400, Lloyd Zusman wrote:
>     >> Lloyd Zusman <ljz <at> asfast.com> writes:
>     >> 
>     >> > In the summary buffer, I'd like to only display messages that
>     >> are > either unread or marked.  I want messages that have been
>     >> read to > become invisible.  Is this possible?
>
>     Yoichi> Use filter folder with condition "flag:any".  Regards, --
>     Yoichi> Yoichi NAKAYAMA
>
> In 2.15.2 (and I assume other versions), this will also display
> answered messages.  I think what Lloyd would like is to filter on (OR
> (flag:Unread ) (flag:Important)).  This seems to work interactively; I
> didn't get as far as working out a one keystroke way of doing it.

Thank you.

Actually, now that I understand this, I realize that flag:digest gives
the exact filtering that I desire.

--

-- 
 Lloyd Zusman
 ljz <at> asfast.com
 God bless you.

(Continue reading)

Lloyd Zusman | 2 Jul 2006 06:02

Re: Hiding messages that are already read?

bremner <at> unb.ca writes:

> A few more small observations:
>
> [ ... ]
>
> 3) I'm pretty sure one could add wl-summary-filter-unread-important to
> the appropriate hook function to start up in filtered mode; then you
> most likely don't want the other hook function I listed. 

It seems to not need it on startup, either.  As long as I have
/flag:digest/ hard-coded in the group name in ~/.folders, it always
seems to start up in filtered mode when I enter the group.

However, I have noticed a problem:

In the following discussion, assume that group doesn't contain any
unread messages.

If at least one message is marked as "important", then the filtering
works fine, and only see those marked messages.  However, if I unmark
them (so that they are no longer "important") and I toggle between the
two modes, I never end up seeing an empty folder.  But if I then mark
one message as important, the filtering works again.

In other words, if I _remove_ all the "important" marks in a folder, the
filtering doesn't work, and all those messages remain visible; if I
remove all but one of the "important" marks, then the filtering works.

Any thoughts?
(Continue reading)

Yoichi NAKAYAMA | 2 Jul 2006 11:18
X-Face
Gravatar

Re: Hiding messages that are already read?

At Sun, 02 Jul 2006 00:02:19 -0400,
Lloyd Zusman wrote:
> However, I have noticed a problem:
> 
> In the following discussion, assume that group doesn't contain any
> unread messages.
> 
> If at least one message is marked as "important", then the filtering
> works fine, and only see those marked messages.  However, if I unmark
> them (so that they are no longer "important") and I toggle between the
> two modes, I never end up seeing an empty folder.  But if I then mark
> one message as important, the filtering works again.
> 
> In other words, if I _remove_ all the "important" marks in a folder, the
> filtering doesn't work, and all those messages remain visible; if I
> remove all but one of the "important" marks, then the filtering works.
> 
> Any thoughts?

I've reproduced the problem. It is a bug of Wanderlust.
I'll investigate it.

Thanks, 
--

-- 
Yoichi NAKAYAMA

Lloyd Zusman | 2 Jul 2006 14:42

Re: Hiding messages that are already read?

Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:

> At Sun, 02 Jul 2006 00:02:19 -0400,
> Lloyd Zusman wrote:
>>
>> [ ... ]
>> 
>> In other words, if I _remove_ all the "important" marks in a folder, the
>> filtering doesn't work, and all those messages remain visible; if I
>> remove all but one of the "important" marks, then the filtering works.
>> 
>> Any thoughts?
>
> I've reproduced the problem. It is a bug of Wanderlust.
> I'll investigate it.

Thank you!

--

-- 
 Lloyd Zusman
 ljz <at> asfast.com
 God bless you.

Yoichi NAKAYAMA | 2 Jul 2006 14:48
X-Face
Gravatar

Re: Hiding messages that are already read?

At Sun, 02 Jul 2006 18:18:17 +0900,
Yoichi NAKAYAMA wrote:
> At Sun, 02 Jul 2006 00:02:19 -0400,
> Lloyd Zusman wrote:
> > However, I have noticed a problem:
> > 
> > In the following discussion, assume that group doesn't contain any
> > unread messages.
> > 
> > If at least one message is marked as "important", then the filtering
> > works fine, and only see those marked messages.  However, if I unmark
> > them (so that they are no longer "important") and I toggle between the
> > two modes, I never end up seeing an empty folder.  But if I then mark
> > one message as important, the filtering works again.
> > 
> > In other words, if I _remove_ all the "important" marks in a folder, the
> > filtering doesn't work, and all those messages remain visible; if I
> > remove all but one of the "important" marks, then the filtering works.
> > 
> > Any thoughts?
> 
> I've reproduced the problem. It is a bug of Wanderlust.
> I'll investigate it.

Following patch describes what is the point of the problem,
but I haven't reached a reasonable fix.
--

-- 
Yoichi NAKAYAMA
Attachment (elmo-filter.el.diff): application/octet-stream, 734 bytes
(Continue reading)

Yoichi NAKAYAMA | 3 Jul 2006 16:12
X-Face
Gravatar

Re: Hiding messages that are already read?

At Sun, 02 Jul 2006 21:48:39 +0900,
Yoichi NAKAYAMA wrote:
> At Sun, 02 Jul 2006 18:18:17 +0900,
> Yoichi NAKAYAMA wrote:
> > At Sun, 02 Jul 2006 00:02:19 -0400,
> > Lloyd Zusman wrote:
> > > However, I have noticed a problem:
> > > 
> > > In the following discussion, assume that group doesn't contain any
> > > unread messages.
> > > 
> > > If at least one message is marked as "important", then the filtering
> > > works fine, and only see those marked messages.  However, if I unmark
> > > them (so that they are no longer "important") and I toggle between the
> > > two modes, I never end up seeing an empty folder.  But if I then mark
> > > one message as important, the filtering works again.
> > > 
> > > In other words, if I _remove_ all the "important" marks in a folder, the
> > > filtering doesn't work, and all those messages remain visible; if I
> > > remove all but one of the "important" marks, then the filtering works.
> > > 
> > > Any thoughts?
> > 
> > I've reproduced the problem. It is a bug of Wanderlust.
> > I'll investigate it.
> 
> Following patch describes what is the point of the problem,
> but I haven't reached a reasonable fix.

Murata-san installed a fix into cvs trunk:
(Continue reading)

Lloyd Zusman | 4 Jul 2006 15:00

Re: Hiding messages that are already read?

Yoichi NAKAYAMA <yoichi <at> geiin.org> writes:

> At Sun, 02 Jul 2006 21:48:39 +0900,
> Yoichi NAKAYAMA wrote:
>> At Sun, 02 Jul 2006 18:18:17 +0900,
>> Yoichi NAKAYAMA wrote:
>> > At Sun, 02 Jul 2006 00:02:19 -0400,
>> > Lloyd Zusman wrote:
>> > >
>> > > [ ... ]
>> > >
>> > > In other words, if I _remove_ all the "important" marks in a folder, the
>> > > filtering doesn't work, and all those messages remain visible; if I
>> > > remove all but one of the "important" marks, then the filtering works.
>
> [ ... ]
>
> Murata-san installed a fix into cvs trunk:
>  http://cvs.m17n.org/viewcvs/root/wanderlust/elmo/ChangeLog?r1=1.789&r2=1.790
>  http://cvs.m17n.org/viewcvs/root/wanderlust/elmo/elmo-filter.el?r1=1.57&r2=1.58
> My problem disappear with it.

My thanks to you and Murata-san!  I will try this later today, and then,
I'll report back here with my results.

--

-- 
 Lloyd Zusman
 ljz <at> asfast.com
 God bless you.

(Continue reading)


Gmane