Re: ":source ~/.muttrc" command weirdly moves message around in
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover: > I originally had this: > ><|cv|dm > > and you suggested this: > >'(<|=cv|=dm)$' > > but the only two things that works are these: > ><|cv|dm and '<|cv|dm' > > No other combination lets it read the%cto the right of the line. Hm. I just tested it. It seems like mutt doesn't want to do more than one shortcut substitution per pattern (I haven't checked the source to double-check, but that's how it seems to behave). I learned something new about mutt! Thanks! I still think you should make your patterns a little tighter, but making them bulletproof won't be as elegant looking. Adding the $ to the end will tighten the pattern without hurting: '(<|cv|dm)$' It's not bulletproof, but that will prevent a lot of false-positives. Another thing you can do is add a separator matcher, so that you can make sure you only match folders of that name, like so: '(<|[./]cv|[./]dm)$' And that should work pretty well also. Finally, for something *really* bulletproof, but much more ugly, you can use $folder directly (rather than the shortcut), because mutt substitutes variables as often as necessary, unlike (apparently) shortcuts. Also, you'd have to use double-quotes, to get mutt to do the right substitution. So, something like this: "(<|$folder[./]cv|$folder[./]dm)$" Use whatever works for you; I just recommend using a tighter pattern when possible. Your original pattern of just two lowercase letters seems to be just begging to match things you don't intend. ~Kyle - -- The purpose of computing is insight, not numbers. -- Richard W. Hamming -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkhXaAUACgkQBkIOoMqOI17L9QCguwQjBsTDV09W1DCeutzp+MS/ GJ8An2st6P8z1WG+oTpH5G3pS6MrhOli =Cshb -END PGP SIGNATURE-
change folder doesn't suggest folder with unread messages
Hi, for quite some time I've been using Mutt. Lately it was Mutt 1.5.13 on Debian etch. It worked great. Last week I upgraded my server to Ubuntu 8.04, and Mutt 1.5.17 and found out that one of the nicest features is gone. Partially. I'm using IMAP to access mailboxes. Have all of them subscribed, and it works great. In Mutt 1.5.13, when I pressed "c" to change folder, Mutt was automatically suggesting "next" folder with unread messages. Now - in 1.5.17 (and 1.5.18 which i tested as well) - it does suggest folder, but not all of them. For example. When I press "y", I get list of all mailboxes with their new messages count: It looks like this: 1 1 imap://127.0.0.1/INBOX 2 0 imap://127.0.0.1/INBOX.archive 3 0 imap://127.0.0.1/INBOX.auta 4 0 imap://127.0.0.1/INBOX.auta.cc 5 1 imap://127.0.0.1/INBOX.backups 6 0 imap://127.0.0.1/INBOX.backups.ok 7 0 imap://127.0.0.1/INBOX.Drafts 8 0 imap://127.0.0.1/INBOX.firmowe 9 0 imap://127.0.0.1/INBOX.important 10 0 imap://127.0.0.1/INBOX.lists 11 0 imap://127.0.0.1/INBOX.lists.pg-admin 12 0 imap://127.0.0.1/INBOX.lists.pg-advocacy 13 0 imap://127.0.0.1/INBOX.lists.pg-announce 14 0 imap://127.0.0.1/INBOX.lists.pg-benchmarks 15 0 imap://127.0.0.1/INBOX.lists.pgbouncer 16 0 imap://127.0.0.1/INBOX.lists.pg-bugs 17 5 imap://127.0.0.1/INBOX.lists.pg-committers 18 0 imap://127.0.0.1/INBOX.lists.pg-general 19 26 imap://127.0.0.1/INBOX.lists.pg-hackers 20 0 imap://127.0.0.1/INBOX.lists.pg-jdbc 21 0 imap://127.0.0.1/INBOX.lists.pg-jobs 22 0 imap://127.0.0.1/INBOX.lists.pg-patches 23 0 imap://127.0.0.1/INBOX.lists.pg-performance 24 0 imap://127.0.0.1/INBOX.lists.pg-planet 25 4 imap://127.0.0.1/INBOX.lists.pg-sql 26 0 imap://127.0.0.1/INBOX.lists.pg-www 27 3 imap://127.0.0.1/INBOX.lists.slony-general 28 0 imap://127.0.0.1/INBOX.outbox 29 0 imap://127.0.0.1/INBOX.postponed 30 0 imap://127.0.0.1/INBOX.Queue 31 0 imap://127.0.0.1/INBOX.sandy 32 0 imap://127.0.0.1/INBOX.sensi 33 0 imap://127.0.0.1/INBOX.sensi.commune 34 0 imap://127.0.0.1/INBOX.sensi.development 35 0 imap://127.0.0.1/INBOX.sensi.imports 36 0 imap://127.0.0.1/INBOX.sensi.jobs-dev 37 0 imap://127.0.0.1/INBOX.sensi.verticals-dev 38 0 imap://127.0.0.1/INBOX.Sent 39 0 imap://127.0.0.1/INBOX.SPAM 40 0 imap://127.0.0.1/INBOX.sysdivision 41 0 imap://127.0.0.1/INBOX.Trash 42 0 imap://127.0.0.1/INBOX.xbox 43 0 imap://127.0.0.1/INBOX.zakupy 44 0 imap://127.0.0.1/INBOX.zb But when I press "c" - it doesn't suggest anything. Couple of minutes ago I had some new mails in lists.pg-general, and this folder *was* suggested to me after "c". I am unable to find any specific pattern which would say when folder is suggested, and when not - yesterday mutt "happily" suggested lists.pg-hackers, but today - no. I know that my problem description might not be enough to help, but maybe it will suggest something to you, so you can point me in right direction. I would really love to stick to mutt, but the fact that I have to go to "list of all folders" to check where are unread messages - it makes usage of mutt practically unbearable. Best regards, depesz
Re: change folder doesn't suggest folder with unread messages
Hi,
> I'm using IMAP to access mailboxes. Have all of them subscribed, and it
> works great.
>
> In Mutt 1.5.13, when I pressed "c" to change folder, Mutt was
> automatically suggesting "next" folder with unread messages.
[...]
> But when I press "c" - it doesn't suggest anything. Couple of minutes
> ago I had some new mails in lists.pg-general, and this folder *was*
> suggested to me after "c".
When you leave folder, mutt will mark all messages as Old. 'y' shows
number of _unread_ messages. 'c' suggests you folders containing 'New'
messages. So once you visit folder, it won't be suggested again unless
there appears new message again.
> I would really love to stick to mutt, but the fact that I have to go
> to "list of all folders" to check where are unread messages - it makes
> usage of mutt practically unbearable.
If I am right about the cause, the attached patch makes mark_old option
work also for IMAP.
Hope this helps
--
Vlad
IMAP mark_old patch
diff --git a/imap/command.c b/imap/command.c
--- a/imap/command.c
+++ b/imap/command.c
@@ -917,7 +917,7 @@
dprint (3, (debugfile, "Found %s in buffy list (OV: %d ON: %d U:
%d)\n",
mailbox, olduv, oldun, status->unseen));
-if (olduv && olduv == status->uidvalidity)
+if (olduv && olduv == status->uidvalidity && option(OPTMARKOLD))
{
if (oldun < status->uidnext)
inc->new = status->unseen;
pgpsN4IucdBFR.pgp
Description: PGP signature
Re: change folder doesn't suggest folder with unread messages
On Tue, Jun 17, 2008 at 11:42:18AM +0200, Vladimir Marek wrote: > > But when I press "c" - it doesn't suggest anything. Couple of minutes > > ago I had some new mails in lists.pg-general, and this folder *was* > > suggested to me after "c". > When you leave folder, mutt will mark all messages as Old. 'y' shows > number of _unread_ messages. 'c' suggests you folders containing 'New' > messages. So once you visit folder, it won't be suggested again unless > there appears new message again. I was *not* visiting the folder before. > > I would really love to stick to mutt, but the fact that I have to go > > to "list of all folders" to check where are unread messages - it makes > > usage of mutt practically unbearable. > If I am right about the cause, the attached patch makes mark_old option > work also for IMAP. I will try it - maybe it will help. will let you know in about an hour. Best regards, depesz
Re: change folder doesn't suggest folder with unread messages
On Tue, Jun 17, 2008 at 11:42:18AM +0200, Vladimir Marek wrote: > If I am right about the cause, the attached patch makes mark_old option > work also for IMAP. OK, checked - it didn't help :( Best regards, depesz
Re: ":source ~/.muttrc" command weirdly moves message around in
Hi,
* Kyle Wheeler wrote:
On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover:
I originally had this:
<|cv|dm
and you suggested this:
'(<|=cv|=dm)$'
but the only two things that works are these:
<|cv|dm and '<|cv|dm'
No other combination lets it read the%cto the right of the line.
Hm. I just tested it. It seems like mutt doesn't want to do more than
one shortcut substitution per pattern (I haven't checked the source to
double-check, but that's how it seems to behave). I learned something
new about mutt! Thanks!
When expanding paths, mutt looks at the first character for a shortcut
only, much like ~-expansion in the shell. That means that
<|cv|dm
will be expanded to
foobar|cv|dm
before being compiled as a regex. In
(<|=cv|=dm)$
there won't be any expansion at all since '(' isn't special at all. To
match mailboxes 'foo' and 'bar' below $folder, something like this could
work:
=(foo|bar)
Rocco
Re: change folder doesn't suggest folder with unread messages
> > If I am right about the cause, the attached patch makes mark_old option > > work also for IMAP. > > OK, checked - it didn't help :( Do you have 'set mark_old = no' in your .muttrc ? Apart from the mark_old thing, mutt's behaving well for me when using IMAP. If you switch to the folder which is not offered by 'c', can you see messages flagged 'N'ew ? Is the folder in your mailboxes list ? -- Vlad pgpsx5HnWvAXh.pgp Description: PGP signature
Re: change folder doesn't suggest folder with unread messages
On Tue, Jun 17, 2008 at 01:46:06PM +0200, Vladimir Marek wrote: > Do you have 'set mark_old = no' in your .muttrc ? Apart from the no. i dont have any mark_old setting in my .,muttrc > mark_old thing, mutt's behaving well for me when using IMAP. If you > switch to the folder which is not offered by 'c', can you see messages > flagged 'N'ew ? Is the folder in your mailboxes list ? yes, and yes. this folder is in "y" output (list of folders), it is subscribed, and the message is shown to be "N". Best regards, depesz
Re: change folder doesn't suggest folder with unread messages
> > Do you have 'set mark_old = no' in your .muttrc ? Apart from the > > no. i dont have any mark_old setting in my .,muttrc > > > mark_old thing, mutt's behaving well for me when using IMAP. If you > > switch to the folder which is not offered by 'c', can you see messages > > flagged 'N'ew ? Is the folder in your mailboxes list ? > > yes, and yes. > > this folder is in "y" output (list of folders), it is subscribed, and > the message is shown to be "N". Hmm, that puzzles me a bit. You don't have any mark_old setting, which means it's set to 'yes' by default. And yet, you can see the mails marked as 'N', even if you switch to different maildir and back, without touching the new file ? At any rate, I'm afraid that I won't be able to help here. -- Vlad pgpK0kyTXBu88.pgp Description: PGP signature
Re: change folder doesn't suggest folder with unread messages
On Tue, Jun 17, 2008 at 03:14:57PM +0200, Vladimir Marek wrote: > Hmm, that puzzles me a bit. You don't have any mark_old setting, which > means it's set to 'yes' by default. And yet, you can see the mails > marked as 'N', even if you switch to different maildir and back, without > touching the new file ? when i switch to another folder and back, N changes to O. > At any rate, I'm afraid that I won't be able to help here. i have got some suspicion about imap server - it got upgraded too. can it be debugged anyway? i can do strace, tcpdump, anything that's neccessary, i just don't know where exactly to look. Best regards, depesz
Re: change folder doesn't suggest folder with unread messages
> i have got some suspicion about imap server - it got upgraded too. > > can it be debugged anyway? i can do strace, tcpdump, anything that's > neccessary, i just don't know where exactly to look. It can, if mutt is compiled with --enable-debug , see 'mutt -v | grep DEBUG'. +DEBUG means that it is compiled in. $ mutt -d level This will log to ~/.muttdebug0. The higher level, the more informations. I tend to use 99. Be warned that the file will contain your password and probably other potentially sensitive data. -- Vlad pgpcgpWZyOXhZ.pgp Description: PGP signature
Re: change folder doesn't suggest folder with unread messages - solved
> for quite some time I've been using Mutt. Lately it was Mutt 1.5.13 on > Debian etch. > > It worked great. > > Last week I upgraded my server to Ubuntu 8.04, and Mutt 1.5.17 and found > out that one of the nicest features is gone. Partially. [...] It boiled down to old header cache. Shouldn't mutt 1.5.17 detect that the hcache data are invalid and discard them ? Or does it depend on hcache backend ? Thank you -- Vlad pgpVMfI0miNIo.pgp Description: PGP signature
archived mail in gmail
I tried Evolution with Gmail using Imap. It sorted my emails by the labels I had been using with the web interface, very nice. Why isn't Mutt doing the same? It's only looking at the email in my Inbox, and I can't get to archived email. My email is automatically archived and labelled using filters in Gmail, so not all my new mail will show up in Inbox. Here's a section from my ~/.muttrc 99 set imap_user = '[EMAIL PROTECTED]' 100 set imap_pass = 'mypassword' 101 set from = "[EMAIL PROTECTED]" 102 set realname = "My Name" 103 set spoolfile = "imaps://imap.gmail.com:993/INBOX" 104 set folder = imaps://imap.gmail.com:993 105 set smtp_url = "smtp://[EMAIL PROTECTED]:587/" 106 set record = "imaps://imap.gmail.com/[Gmail]/Sent Mail" 107 set postponed = "imaps://imap.gmail.com/[Gmail]/Drafts" 108 set header_cache = "~/.mutt/cache/headers" 109 set message_cachedir = "~/.mutt/cache/bodies" 110 set certificate_file = "~/.mutt/certificates"
Re: archived mail in gmail
On Tue, Jun 17, 2008 at 03:37:20PM -0700, Chris Lemire wrote: > I tried Evolution with Gmail using Imap. It sorted my emails by the labels I > had been using with the web interface, very nice. Why isn't Mutt doing the > same? It's only looking at the email in my Inbox, and I can't get to archived > email. My email is automatically archived and labelled using filters in > Gmail, so not all my new mail will show up in Inbox. Here's a section from my > ~/.muttrc try 'set imap_check_subscribed'. 'man muttrc' has more info. Jamie
Re: latin1: german umlauts not displayed correctly
On Jun 11 02:07, Chris Bannister wrote: > On Tue, Jun 10, 2008 at 01:53:16PM +0200, Steve S wrote: > > My locale settings are > > > > -- > > LANG=en_US.UTF-8 > > LC_CTYPE="en_US.UTF-8" > > LC_NUMERIC="en_US.UTF-8" > > LC_TIME="en_US.UTF-8" > > LC_COLLATE="en_US.UTF-8" > > Consider setting LC_COLLATE="C" > > That way the output from ls -l will be more easily readable, although > you may prefer the output with the current setting. :-) Hmm good, thanks :) steve
