Re: Using TAB to check for new messages
Eduardo Chappa <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
*** Tim K. (Gmane) ([email protected]) wrote in the pine-info...: :) The problem I'm having is that when I hit TAB while viewing the default :) inbox, sometimes pine detects recent messages in the other incoming :) folders, other times it doesn't (and it seems to favor not detecting :) recent messages!). :) :) This feature seems to be very unreliable, unless there are some options :) that I can tweak to make it work better. I definitely do not want the :) option "tab-uses-unseen-for-next-folder" as I usually keep messages :) marked as New in my inboxes. Tim, Do you use the IMAPSTATUS token in the index-format?. If not, make sure you use it. A recent message is marked as "N" or "R", while and unseen message is marked as "U" when you use IMAPSTATUS. If you have never tweaked the index-format variable, then both recent and unseen messages are marked as "N". This will only lead you to confusion. If you use tab-uses-unseen-for-next-folder, then Pine will open the next folder if there are unseen (but maybe none recent) messages. If you only want to use tab to check for recent messages, then unset this feature. The down side, though, is that since Pine keeps (a certain number of) streams open then Pine keeps those imap folders open. The down side of this method is the following situation: * You open a folder in an IMAP server, * You (believe that you) close that folder * While the folder is "closed", a new message arrives * You quit Pine or at least 25 minutes have elapsed since the last time you closed this folder. Under this sequence of events, the next time (you open Pine and) you open that IMAP folder, the "new" messages will be tagged UNSEEN, because they are not recent anymore. A message can only be recent on one session, and that one is the one that you thought you had closed, but Pine did not. If you want to avoid this problem, set the variable max-remote-connections to 0 (zero). The help text makes me believe that this may not work fully, but I believe it will work if your inbox and this folder are in different servers. The help text is not clear about how setting the max-remoe-connection value to zero may fail in this situation. Does this help? -- Eduardo Patches/Help: http://www.math.washington.edu/~chappa/pine/ XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml Please send spam to webmaster@localhost _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info