Re: automatically check for new mail
On Mon, Jan 28, 2008 at 09:22:49PM -0300, Leonardo Caldas wrote: On Mon, Jan 28, 2008 at 06:33:17PM +0100, Steve S wrote: Hi I'm new to mutt, so this question my have been asked before (I found nothing on the web/in the wiki etc.). In my muttrc I have bind browser n check-new which works ok. I hit `n` manually from time to time to see if there is new mail. Is it possible to do that automatically in the background (ala cron)? s. Here I run fetchmail -d 180, which puts a fetchmail proccess into daemon mode and rerun it each 180 sec period. I'm doing that too, with getmail and a cronjob. The problem is not that mail doesn't download to my machine, but that mutt, if * it is open all the time * showing the file browser (when invoked with `mutt -y`) * no key is pressed doesn't show the 'N' flag for folders (mailboxes) which have new mail after $timeout seconds as it should (it should, right? :). It does that only if I a) go to some mailbox and then back to the browser (which is the event a key is pressed and mutt checks for new mail if I understand correctly) b) invoke the check-new function manually. s.
Re: automatically check for new mail
Steve S [EMAIL PROTECTED] wrote: I'm doing that too, with getmail and a cronjob. Nice to hear :). The problem is not that mail doesn't download to my machine, but that mutt, if * it is open all the time * showing the file browser (when invoked with `mutt -y`) * no key is pressed doesn't show the 'N' flag for folders (mailboxes) which have new mail after $timeout seconds as it should (it should, right? :). It does that only if I a) go to some mailbox and then back to the browser (which is the event a key is pressed and mutt checks for new mail if I understand correctly) b) invoke the check-new function manually. Pardon me for being late to this discussion. Have you set `mail_check` to a non-default value in your .muttrc (or system-wide Muttrc) file? Or how about `timeout`? The default for that is 10 minutes -- have you tried waiting that long to see if mutt identifies new mail? Charles -- -- Charles Cazabon [EMAIL PROTECTED] Software, consulting, and services available at http://pyropus.ca/ --
Re: automatically check for new mail
On Tue 29.Jan'08 at 23:10:54 +0100, Steve S wrote: On Tue, Jan 29, 2008 at 12:29:55PM -0600, Charles Cazabon wrote: Pardon me for being late to this discussion. Have you set `mail_check` to a non-default value in your .muttrc (or system-wide Muttrc) file? Or how about `timeout`? iThe default for that is 10 minutes -- have you tried waiting that long to see if mutt identifies new mail? Default values are the ones mentioned in the manual: $timeout=600, $mail_check=5. I played with them by setting them to small values for testing: $timeout=10, $mail_check=5 or $timeout=60, $mail_check=30 but the 'N' flag just won't appear automatically if the browser is focused all the time. Would it help posting my .muttrc? I suspect either a stupid newbie-related misconfig or an issue with my Debian mutt version (since I saw they include some patches on their own which are not in the official mutt tree). I have a similar configuration, and now that I have taken a better look, I basically have the same problem. I haven't noticed it since I use the sidebar patch. Anyway, I wonder if there are some consistency issues between the values stored in timeout and mail_check that could be causing the problem.
Re: automatically check for new mail
On Tue, Jan 29, 2008 at 12:29:55PM -0600, Charles Cazabon wrote: Steve S [EMAIL PROTECTED] wrote: The problem is not that mail doesn't download to my machine, but that mutt, if * it is open all the time * showing the file browser (when invoked with `mutt -y`) * no key is pressed doesn't show the 'N' flag for folders (mailboxes) which have new mail after $timeout seconds as it should (it should, right? :). It does that only if I a) go to some mailbox and then back to the browser (which is the event a key is pressed and mutt checks for new mail if I understand correctly) b) invoke the check-new function manually. Pardon me for being late to this discussion. Have you set `mail_check` to a non-default value in your .muttrc (or system-wide Muttrc) file? Or how about `timeout`? iThe default for that is 10 minutes -- have you tried waiting that long to see if mutt identifies new mail? Default values are the ones mentioned in the manual: $timeout=600, $mail_check=5. I played with them by setting them to small values for testing: $timeout=10, $mail_check=5 or $timeout=60, $mail_check=30 but the 'N' flag just won't appear automatically if the browser is focused all the time. Would it help posting my .muttrc? I suspect either a stupid newbie-related misconfig or an issue with my Debian mutt version (since I saw they include some patches on their own which are not in the official mutt tree). s.
[NCLASSIFIED]push 'collapse-all' - Question ...
Hi all,
I have the following default folder-hook:
folder-hook . \
set sort=reverse-threads ;\
set sort_aux=last-date-received ;\
push 'collapse-all' ;\
set index_format=%3N %4C %Z %{%b %d} %-15.15F (%4c) %?M?%M ?%s ;\
set display_filter='t-prot -acelmtS -Mmutt --spass'
When I first exec mutt(1) all threads are collapsed (intended behaviour).
However, if I 'c' +another_folder and then 'c' ! (back to my INBOX) all threads
will be _always_ expanded (not intended behaviour).
So, how can I make push 'collapse-all' persist regardless of whether or not
what folder(s) I change into and how many times I change into them ? I just want
all my threads to be collapsed at all times unless I explicitly expand them.
Any hot tips would be much appreciated!
-aW
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
