Discussion:
Key binding?
Claus Atzenbeck
2008-01-24 08:11:03 UTC
Permalink
Hi all:

I have one folder in which I only read subjects. After that I mark all
mails as being read by pressing: ;aa*!n

I do this regularly. Is there a workaround in Alpine (running on Mac OS
X) which would let me map these 8 keystrokes (two of them are shift) to
one key?

Cheers,
Claus
Jonesy
2008-01-26 03:15:40 UTC
Permalink
Post by Claus Atzenbeck
I have one folder in which I only read subjects. After that I mark all
mails as being read by pressing: ;aa*!n
I do this regularly. Is there a workaround in Alpine (running on Mac OS
X) which would let me map these 8 keystrokes (two of them are shift) to
one key?
Exit the folder and [d]elete the folder?

Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
38.24N 104.55W | @ config.com | Jonesy | OS/2
*** Killfiling google posts: <http://jonz.net/ng.htm>
Claus Atzenbeck
2008-02-25 10:41:33 UTC
Permalink
Post by Jonesy
Post by Claus Atzenbeck
I have one folder in which I only read subjects. After that I mark all
mails as being read by pressing: ;aa*!n
I do this regularly. Is there a workaround in Alpine (running on Mac OS
X) which would let me map these 8 keystrokes (two of them are shift) to
one key?
Exit the folder and [d]elete the folder?
No, I don't want to delete the complete folder, but mark all messages as
being read. I would like to have a shortcut for ";aa*!n", but Pine does
not allow me to define shortcuts.

(BTW, sorry for answering so late, but I overlooked this message
earlier.)

Claus
Eduardo Chappa
2008-02-25 17:36:33 UTC
Permalink
On Mon, 25 Feb 2008, Claus Atzenbeck wrote:

:) No, I don't want to delete the complete folder, but mark all messages
:) as being read. I would like to have a shortcut for ";aa*!n", but Pine
:) does not allow me to define shortcuts.

Here is an idea. Use a filter to do this, and you will not have to press
any keys. This is the idea: make the filter act when the folder is being
opened, rather than when the folder is being closed. The point is that you
probably care more that the message is tagged as read rather than when it
is tagged unread.

You could try defining a filter that is activated for

Message is New (Unseen)? =
(*) Yes

Message is Recent? =
(*) No

Filter Action =
(*) Just Set Message Status

Set New Status =
Set Choose One
--- --------------------
( ) Don't change it
( ) Set this state
(*) Clear this state

Does that work for you?
--
Eduardo
http://staff.washington.edu/chappa/pine/
Claus Atzenbeck
2008-02-25 19:39:01 UTC
Permalink
Post by Eduardo Chappa
Here is an idea. Use a filter to do this, and you will not have to press
any keys. This is the idea: make the filter act when the folder is being
opened, rather than when the folder is being closed. The point is that you
probably care more that the message is tagged as read rather than when it
is tagged unread.
I tested that. Thanks for pointing that out. The disadvantage, however,
is that Alpine seems to change the flag to unread on message delivery.
That means that the unread message count at the folder index does not
count new messages. Also, the tab (jumping to the next folder with
unread messages) does not consider the folder, since all messages are
set unread.

I have a workaround, which is not perfect either: I use the terminal
application to send the ;aa*!n string when a certain key combination is
pressed. It works, but actually it should be handled by Alpine.

I can live with my workaround for now. Possibly one of the next versions
will have that feature.

Cheers,
Claus
Eduardo Chappa
2008-02-25 21:49:16 UTC
Permalink
On Mon, 25 Feb 2008, Claus Atzenbeck wrote:

:) On Mon, 25 Feb 2008, Eduardo Chappa wrote:
:)
:) > Here is an idea. Use a filter to do this, and you will not have to
:) > press any keys. This is the idea: make the filter act when the folder
:) > is being opened, rather than when the folder is being closed. The
:) > point is that you probably care more that the message is tagged as
:) > read rather than when it is tagged unread.
:)
:) I tested that. Thanks for pointing that out. The disadvantage, however,
:) is that Alpine seems to change the flag to unread on message delivery.

That should not be the case. The filter has a "Message is recent" set to
no, so only messages that are not recent should match this. Are you doing
this over IMAP or on a local mailbox? (that could make a difference)

:) That means that the unread message count at the folder index does not
:) count new messages.

That seems right. Unread and Recent are two different concepts. If you
want to know about new messages, you should be asking the recent count,
not the unread count.

:) Also, the tab (jumping to the next folder with unread messages) does
:) not consider the folder, since all messages are set unread.

That is very interesting.

:) I have a workaround, which is not perfect either: I use the terminal
:) application to send the ;aa*!n string when a certain key combination is
:) pressed. It works, but actually it should be handled by Alpine.

That seems like a work around that should work. I would tell you about one
of my patches that actually does what you want, but I thought that your
problem could be handled by filters so there would be no need to patch
pine/alpine. Nevertheless, there is a patch that does what you want.
--
Eduardo
http://staff.washington.edu/chappa/pine/
Claus Atzenbeck
2008-02-25 22:29:31 UTC
Permalink
Post by Eduardo Chappa
That should not be the case. The filter has a "Message is recent" set to
no, so only messages that are not recent should match this. Are you doing
this over IMAP or on a local mailbox? (that could make a difference)
Over IMAP. But actually, I ignored "Message is recent", thinking that
all messages should match that rule.

Cheers,
Claus.

Continue reading on narkive:
Loading...