Re: Menu colors are awful in arch
Hi, * anon anon wrote: This is the mutt -v output for Arch where it's not so nice: http://pastebin.com/m40cf5598 This one is built using slang instead of ncurses terminal library. Do you have any chance to build with ncurses? I'm not sure, but I think what you describe is a problem for mutt+slang only. Rocco
Re: How to let mutt always mark mbox as new if it contains new
Hi, * Cameron Simpson wrote: No need. For unvisited mboxen the behaviour is already ok. It is that mutt's sync of the folder on exit sets mtime==atime that causes the trouble. For some people that's what they want (I've visited it so don't bug me until something _extra_ arrives) but for the OP and yourself mutt should have a mode to update the atime post close if there are outstanding messages in N state. There's no need for an additional option, the definition of something extra is already covered by the distinction between old and unread mail in mutt. If there's new mail, mutt should always tell you. If you want to come back to new mail later, set mark_old. Rocco
Re: How to let mutt always mark mbox as new if it contains new
Hi, * Wu, Yue wrote: Thank you, 'check_mbox_size' does the trick. Hmm, how is the partition with the mboxes mounted? This option only exists for setups where access/modification time cannot be reliably used to detect new mail. Filesystems can be mounted to not update atime as that causes disk updates but provides little to no benefit for most applications so many people turn atime updates off. Rocco
Re: How to let mutt always mark mbox as new if it contains new
Hi, * Wu, Yue wrote: Currently, I find that if I enter to a mbox, then quit from it, the mbox's N mark will be removed, no matter whether there are news mails in it or not, not what I think preference for me. Can I configure it? I have set the mark_old=no Hmm, is this by any chance the same as: http://dev.mutt.org/trac/ticket/1362 ? Rocco
Re: utf8 file corruption after transmission over email
Hi, * Jussi Peltola wrote: On Fri, May 08, 2009 at 06:23:15PM -0700, zion wrote: if LC_CTYPE is unset, file doesn't get corrupted. In that case, what does ':set ?charset' in mutt report? I think mutt is reading your file, assuming it's KOI8-R as stated in your locale, and converting it to UTF-8 for sending. It has to do that; plain text won't tell it what charset it's in and it has to guess. Yes. If mutt is recent enough, $attach_charset can help (it specifies the charsets to use for guessing for text media type attachments). Rocco
Re: Why does mutt sees Mailman mailboxes as empty?
Hi M.! On Sa, 09 Mai 2009, M. Fioretti wrote: My real interest was testing automated mbox-maildir automatic conversion via mutt on some sample email that I needed to analyze anyway, this issue was really unexpected. I have been doing something like this using mutt. For those that understand German I have once documented this approach here: http://blog.256bit.org/archives/345-Mutt-als-Mailbox-Konvertierer.html in short: you create a simple muttrc file like this: ,[ muttrc_convert ]- | # Specify your target type | # use one of | # Maildir, MH, mbox und MMDF | set mbox_type=Maildir | | # Where to store the mails | # the path needs to exist! | set my_archivedir=~/mutt_archive/$mbox_type | | # Create new mails, without confirmation | set confirmcreate=no | | # append mails without confirmation | set confirmappend=yes | | # quit without confirmation | set quit=yes | | folder-hook . 'push tag-pattern~Aenter\ | tag-prefixcopy-messagekill-line\ | $my_archivedirenterquit' ` and then start mutt like this: mutt -F muttrc_convert -f mbox_file This won't touch your original mbox file only read it and then store your mails in the desired format at ~/mutt_archive as either Maildir, MH, mbox or MMDF depending on your output format. HTH, Christian -- hundred-and-one symptoms of being an internet addict: 234. You started college as a chemistry major, and walk out four years later as an Internet provider.
Re: doubled messages by copying
Hello, You just want to move messages? Then use s (save-message), which copies the message to whatever mailbox you specify, then marks the copy in the current mailbox as deleted. Thank you Monte, Christian, Gary and Noah. Embarrassingly i wasn't aware of save-message. I realize that the german explanation of its function (nachricht in datei speichern = save to a file) confused me into thinking save-message would produce some file outside of mutts mbox format. Monte's Macro is a nice find for me. I will keep my eyes peeled for the original problem of doubled messages anyhow. jan
Re: doubled messages by copying
On Tue, May 12, 2009 at 11:22:46AM +0200, Jan-Herbert Damm wrote: Embarrassingly i wasn't aware of save-message. I realize that the german explanation of its function (nachricht in datei speichern = save to a file) confused me into thinking save-message would produce some file outside of mutts mbox format. Hardly embarrassing, I'd say. Even though I've known for a long time what save-message does, both its name and the explanation (the English docs also say save to a file) don't sound right to me. They suggest the message is saved to e.g. a .txt file, not that it is simply moved to another mail folder. -- Joost Kremers Life has its moments
Re: doubled messages by copying
On Tue, May 12, 2009 at 11:39:23AM +0200, Joost Kremers wrote: On Tue, May 12, 2009 at 11:22:46AM +0200, Jan-Herbert Damm wrote: Embarrassingly i wasn't aware of save-message. [..] Hardly embarrassing, [..] I had similar troubles at first as well. Perhaps the wording of that command's description comes from mbox, in which moving a mail to another mailbox really is little more than saving the message to a file. By any chance was Mutt originally developed with only mbox support, and then Maildir support added later on? -- Noah Sheppard Assistant Computer Resource Manager Taylor University CSE Department nshep...@cse.taylor.edu
Is this a mutt issue or a links issue (HTML display)
I am using links to display HTML messages in mutt on two different systems and I'm confused as to why I'm seeing differently formatted output. On one system each link has a reference number by it and the reference URLs are listed at the bottom of the page. On the other system I don't see these references. I want the references. E.g. on one system I see:- [-- Autoview using links -dump '/tmp/mutt.html' --] [1]Amazon.co.uk Keeping your Amazon account secure is one of our most important ... ... ... References Visible links 1. http://www.amazon.co.uk/exec/obidos/tg/browse/-/468294 Whereas on the other system I don't see that [1] nor the references at the bottom, i.e. I just get:- [-- Autoview using links -dump '/tmp/mutt.html' --] Amazon.co.uk Keeping your Amazon account secure is one of our most important Both systems have the same entry for links in the mailcap file, both systems have near identical muttrc files. Is this some sort of oddity in the way that mutt is handing the HTML to links or is links working differently for some reason? -- Chris Green
Re: Is this a mutt issue or a links issue (HTML display)
On Tue, May 12, 2009 at 01:56:41PM +0100, Chris G wrote: I am using links to display HTML messages in mutt on two different systems and I'm confused as to why I'm seeing differently formatted output. [...] Both systems have the same entry for links in the mailcap file, both systems have near identical muttrc files. What about ~/.links/links.conf or ~/.elinks/elinks.conf? Is this some sort of oddity in the way that mutt is handing the HTML to links or is links working differently for some reason? You may want to save the HTML message part to a file, then run links -dump against it on both systems. That takes mutt out of the equation, so you can determine whether or not mutt is part of the problem. You can save just the HTML message part by selecting the email in the index, using view-attachments (by default bound to v), selecting the HTML part, and using save-entry (by default bound to s) to save it to a file. Ed signature.txt Description: Digital signature
Re: Why does mutt sees Mailman mailboxes as empty?
Hi, * Christian Brabandt wrote: I have been doing something like this using mutt. For those that understand German I have once documented this approach here: http://blog.256bit.org/archives/345-Mutt-als-Mailbox-Konvertierer.html Regarding that entry: compressed folders support is not in the mainline. in short: you create a simple muttrc file like this: [...] and then start mutt like this: mutt -F muttrc_convert -f mbox_file This won't touch your original mbox file only read it and then store your mails in the desired format at ~/mutt_archive as either Maildir, MH, mbox or MMDF depending on your output format. Two comments: First, mutt does more than is necessary when saving messages or opening folders, so a formail+procmail combination may be more suitable. To speed things up a little, you should try to use the -n switch and see if that speeds things up a little. Rocco
Re: Is this a mutt issue or a links issue (HTML display)
On Tue, May 12, 2009 at 01:56:41PM +0100, Chris G wrote: Is this some sort of oddity in the way that mutt is handing the HTML to links or is links working differently for some reason? from 'man links': -html-numbered-links 0/1 Number links in text mode. Allow quick link selection by typing link number and enter. i would guess your links is configured differently on the two systems. at the very least, adding this option in your .mailcap should give you numbered links. HTH -- Joost Kremers Life has its moments
Unsubscribe
unsubscribe
Re: doubled messages by copying
Hi, * Joost Kremers wrote: Hardly embarrassing, I'd say. Even though I've known for a long time what save-message does, both its name and the explanation (the English docs also say save to a file) don't sound right to me. They suggest the message is saved to e.g. a .txt file, not that it is simply moved to another mail folder. I've fixed that to be consistent with the description for copy-message. It won't get any better as the description is shared with save-entry in the attachment menu. Rocco
Re: Is this a mutt issue or a links issue (HTML display)
On Tue, May 12, 2009 at 03:19:55PM +0200, Joost Kremers wrote: On Tue, May 12, 2009 at 01:56:41PM +0100, Chris G wrote: Is this some sort of oddity in the way that mutt is handing the HTML to links or is links working differently for some reason? from 'man links': -html-numbered-links 0/1 Number links in text mode. Allow quick link selection by typing link number and enter. i would guess your links is configured differently on the two systems. at the very least, adding this option in your .mailcap should give you numbered links. Ah, thank you, adding that option has got me the output I wanted. I'm still not sure why the two systems are different though as there's no configuration file on either. Maybe there's some global configuration somewhere. -- Chris Green
Re: How to let mutt always mark mbox as new if it contains new
On 2009-05-12, Rocco Rutte pd...@gmx.net wrote: Hi, * Wu, Yue wrote: Thank you, 'check_mbox_size' does the trick. Hmm, how is the partition with the mboxes mounted? This option only exists for setups where access/modification time cannot be reliably used to detect new mail. Filesystems can be mounted to not update atime as that causes disk updates but provides little to no benefit for most applications so many people turn atime updates off. In my case, at work, almost everything except /tmp is NFS-mounted, including $MAIL and $HOME. I've been using +BUFFY_SIZE and now 'check_mbox_size' for so long that I don't remember exactly the problem I was having without it, except that notifications of new mail and/or mailbox statuses were not working correctly. At home, I'm using Cygwin's mutt package and it just happens to have +BUFFY_SIZE configured. Regards, Gary
Re: Why does mutt sees Mailman mailboxes as empty?
Hi Rocco! On Di, 12 Mai 2009, Rocco Rutte wrote: Hi, * Christian Brabandt wrote: http://blog.256bit.org/archives/345-Mutt-als-Mailbox-Konvertierer.html Regarding that entry: compressed folders support is not in the mainline. Thanks, I'll add a note. BTW: What's the reason, it is not included? I find it incredibly useful. Two comments: First, mutt does more than is necessary when saving messages or opening folders, so a formail+procmail combination may be more suitable. Yeah, but I usually do not fiddle with procmail/formail since I use Sieve and thus it was a lot easier for me to figure that task out using mutt than to install and configure procmail. But YMMV of course. To speed things up a little, you should try to use the -n switch and see if that speeds things up a little. Thanks, I'll add a note. But anyway, speed wasn't an issue for me and it just works™. regards, Christian -- hundred-and-one symptoms of being an internet addict: 236. You start saving URL's in your digital watch.
Re: How to let mutt always mark mbox as new if it contains new
Hi, * Wu, Yue wrote: Currently, I find that if I enter to a mbox, then quit from it, the mbox's N mark will be removed, no matter whether there are news mails in it or not, not what I think preference for me. Can I configure it? I have set the mark_old=no Sorry for the noise. This is just for the record and archives. Whenever your new mail status on mbox folders is broken, you can give fix-atime a try. It's available from: ftp://ftp.mutt.org/mutt/contrib/ Rocco
Re: wrong charset
* El 08/05/09 a las 17:47, Kyle Wheeler chamullaba: On Friday, May 8 at 06:08 PM, quoth Luis A. Florit: But I have three charsets: $charset=//TRANSLIT ?charset=utf-8 What? That doesn't make any sense. Are those two lines actually in your muttrc? The only thing in my .muttrc is 'set charset=//TRANSLIT'. Try removing that from your muttrc entirely. I did it, and mutt sets charset=utf-8. But no matter how I change that, the result is always utf-8. H. That suggests that something somewhere else is changing it. Is there a systemwide muttrc that's setting the $charset maybe? If you tell mutt to use a null muttrc (e.g. `mutt -F /dev/null`) does it still say that $charset is utf-8? When I do ':set charset' I get 'charset=//TRANSLIT' (as expected, although in this case it means UTF-8 despite of the fact that my xterm is ISO-8859-1). What makes you think it means utf-8? Because ':set ?charset' gives 'charset=utf-8', and because the accented characters appear as garbage. If I change to iso-8859-1, I get accented characters as \123. That's because your $charset doesn't match your locale. Even exporting LC_ALL=pt_PT gives \NNN. In any case, a value of iso-8859-1//TRANSLIT should remedy that. No, still as \NNN... I have always used as locale 'LANG=en_US' in a ISO-8859-1 rxvt console, and 'charset=\\TRANSLIT' or iso-8859-1 in muttrc, and everything worked fine. So I don't think this has to do with locales. It seems that mutt does not understand the osso-xterm...? The terminal shouldn't matter in this case. Perhaps I should have said this before, but I use the very same .muttrc in Fedora and Nokia. Both Fedora's iso-8859-1 rxvt and xterm show chars perfectly. It's the Nokia that doesn't. And both have the same locales: everything as en_US. What could it be, but the console? Okay, before we get too twisted up here, first, let's make sure your locale setup is correct. Since perl is usually sensitive to proper locale settings, try doing this: perl -e That SHOULD do nothing at all. Yep, nothing. If it complains, then your locale settings are invalid. To prove that it will complain if your locale is invalid, try this: env LC_ALL=nocharset perl -e That *should* generate a big ugly warning. Yep, it did... But, if perl is happy and mutt with a null config file thinks $charset should be utf-8, then your pt_BR locale is set up to only work with utf-8. In fact, I've never set LANG to be anything but plain en_US with no problems. 1. When you run mutt, it reports that the charset it thinks is appropriate is utf-8 Yes, if I use 'set charset=//TRANSLIT' So... don't do that. I tried with everything... 2. Nothing you seem to do can convince mutt to avoid utf-8 No, now it accepts 'set charset=iso-8859-1', but still displays accented characters as \123. Right. Because the $charset doesn't match the locale environment settings (i.e. what your computer thinks the charset should be based on the LANG and/or LC_CTYPE variables isn't iso-8859-1 for some reason). Perhaps all the Nokia locales are UTF-8 based...? Thanks a lot for your efforts, Kyle!!! Best, L.
Re: wrong charset
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, May 12 at 02:56 PM, quoth Luis A. Florit: I did it, and mutt sets charset=utf-8. On the Nokia? Then the Nokia's locales must all be UTF-8-only. Because ':set ?charset' gives 'charset=utf-8', and because the accented characters appear as garbage. Okay, so, it would appear that the correct character set (the only one your locales support) is utf-8. The next question is: why do the accented characters appear as garbage? But let's first be clear: when LANG is correctly set to pt_PT and mutt has correctly detected $charset to be 'utf-8', do the accented characters show up as \123 or do they show up as random characters, such as: ’ ? If it shows up as random characters, then it would seem to me that the Nokia is *lying*; that its terminal is, in fact, incapable of understanding UTF-8, because it's being sent valid UTF8 character codes and is treating them as Windows-1252 characters instead. However, if it shows up as \123, then for some reason, mutt thinks that those characters are non-printable, and is attempting to mask them. In this case, what may be happening is that the underlying libraries that mutt relies on are broken and/or unreliable. To work around these problems, you may need to recompile mutt (and reconfigure it). Specifically, when you run mutt's ./configure program, add the - --without-wc-funcs and maybe add the --enable-locales-fix. Here's what mutt's build documentation has to say about these: --enable-locales-fix on some systems, the result of isprint() can't be used reliably to decide which characters are printable, even if you set the LANG environment variable. If you set this option, Mutt will assume all characters in the ISO-8859-* range are printable. If you leave it unset, Mutt will attempt to use isprint() if either of the environment variables LANG, LC_ALL or LC_CTYPE is set, and will revert to the ISO-8859-* range if they aren't. If you need --enable-locales-fix then you will probably need --without-wc-funcs too. However, on a correctly configured modern system you shouldn't need either (try setting LANG, LC_CTYPE, or LC_ALL instead). --without-wc-funcs by default Mutt uses the functions mbrtowc(), wctomb() and wcwidth() provided by the system, when they are available. With this option Mutt will use its own version of those functions, which should work with 8-bit display charsets, UTF-8, euc-jp or shift_jis, even if the system doesn't normally support those multibyte charsets. If you find Mutt is displaying non-ascii characters as octal escape sequences (e.g. \243), even though you have set LANG and LC_CTYPE correctly, then you might find you can solve the problem with either or both of --enable-locales-fix and --without-wc-funcs. Does that make sense? The terminal shouldn't matter in this case. Perhaps I should have said this before, but I use the very same .muttrc in Fedora and Nokia. Both Fedora's iso-8859-1 rxvt and xterm show chars perfectly. It's the Nokia that doesn't. And both have the same locales: everything as en_US. What could it be, but the console? More likely than not, it's the system's string manipulation libraries. There are, of course, more things that can go wrong. The terminal may be the problem (but it's usually not), you may also not have the right fonts for the terminal, etc. etc. But those are unusual problems these days, and library and/or locale issues are far more common. I'm operating on the zebra principle here: if you hear hoofbeats, think horses, not zebras. I suppose it *could* be the terminal, but let's eliminate the other options first. perl -e That SHOULD do nothing at all. Yep, nothing. Excellent! Perhaps all the Nokia locales are UTF-8 based...? Probably. Which would make it all the more annoying if their string manipulation libraries cannot handle UTF-8. ~Kyle - -- Brilliance is like four-wheel drive; it enables a person to get stuck in even more remote places. -- Garrison Keillor -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKCb+PAAoJECuveozR/AWeNNMP/jnz8JoM6ABSOGOlrrIPmabx xKvfTT7uTqhyo+cfgGSXTjqiTiThXAEWoPb1KDbDX5EC+0rU4xmdyWDpAzHaqidq wYKEJP0keVXNWp0+lO3qwOtJWSs+DBpUqGgbZ8ZQ0TUfy3xsyT2TD6rTjdUzjjyw ZyEGwkUTbwLSl7BaBwrzSXWvPQXeFlI2wTbzM4IHZswnMBLQOtQIylg5LSIFl2Kn 1XbdepEkOoCj9WXcyLXRCc3mmWFxl4POaSeydCr7Z+H/TdwP734KZqqzscvZHbeP xjMPGSm9b3moZRX7jjwsWUTOIXtpEO22A/adtxPFE/qFoxR8yvA1gEfOCK+elFLu FBswMAQcaZa6u4dzY1XtEKYZdqeZXZbJZUS+LX2PQmvvBYJun3C7Jhrj3YtuixU9 5JHA+gp+tqdSxjz8o4wK4c9qAl+MPeSn039mUBx8uzh8rMDVOe1XtwwLM5OVMa+e qJmo3lqRNdVds/vhRnogdsfoI07WNksTbNhYYTAcCSl6vDCTXf/Q9IvJaSF5VBNj
Re: How to let mutt always mark mbox as new if it contains new
On Tue, May 12, 2009 at 09:40:52AM +0200, Rocco Rutte wrote: Hi, * Wu, Yue wrote: Thank you, 'check_mbox_size' does the trick. Hmm, how is the partition with the mboxes mounted? This option only exists for setups where access/modification time cannot be reliably used to detect new mail. Filesystems can be mounted to not update atime as that causes disk updates but provides little to no benefit for most applications so many people turn atime updates off. I have little acknowledge on it, so I can't give you the sure answer, sorry :( I'm on FreeBSD 7, ~/.mutt is on the /user filesystem, it's mounted by: /dev/ad2s2e /usrufs rw 2 2 in the /etc/fstab. I don't know if atime is enabled by default or not. About the patch you advise, I'm really not familiar with programming relative stuff and got a little busy these days, so I'm afraid I can't have a try, sorry! -- Hi, Wu, Yue
Re: How to let mutt always mark mbox as new if it contains new
On Tue, May 12, 2009 at 07:04:39AM -0700, Gary Johnson wrote: On 2009-05-12, Rocco Rutte pd...@gmx.net wrote: Hi, * Wu, Yue wrote: Thank you, 'check_mbox_size' does the trick. Hmm, how is the partition with the mboxes mounted? This option only exists for setups where access/modification time cannot be reliably used to detect new mail. Filesystems can be mounted to not update atime as that causes disk updates but provides little to no benefit for most applications so many people turn atime updates off. In my case, at work, almost everything except /tmp is NFS-mounted, including $MAIL and $HOME. I've been using +BUFFY_SIZE and now 'check_mbox_size' for so long that I don't remember exactly the problem I was having without it, except that notifications of new mail and/or mailbox statuses were not working correctly. At home, I'm using Cygwin's mutt package and it just happens to have +BUFFY_SIZE configured. Just a comment. I compiled 1.5.18 out of the box on Cygwin and I do not have that set. I am not sure what it does, but would it be best set in the cygwin version. Brian. Regards, Gary -- I have attempted to give you a glimpse...of what there may be of soul in chemistry. But it may have been in vain. Perchance the chemist is already damned and the guardian of the pearly gates has decreed that of all the black arts, chemistry is the blackest. But if the chemist has lost his soul, he will not have lost his courage and as he descends into the inferno, sees the rows of glowing furnaces and sniffs the homey fumes of brimstone, he will call out--: 'Asmodeus, hand me a test-tube' * G. N. Lewis (1875-1946)* Brian Salter-Duke (Brian Duke) Email: b_duke(AT)bigpond(DOT)net(DOT)au
Re: How to let mutt always mark mbox as new if it contains new
On 2009-05-13, Brian Salter-Duke b_d...@bigpond.net.au wrote: On Tue, May 12, 2009 at 07:04:39AM -0700, Gary Johnson wrote: At home, I'm using Cygwin's mutt package and it just happens to have +BUFFY_SIZE configured. Just a comment. I compiled 1.5.18 out of the box on Cygwin and I do not have that set. I am not sure what it does, but would it be best set in the cygwin version. I don't know. I suppose if you're not experiencing any of the new-mail status/notification problems discussed in this thread, you don't need it. Regards, Gary
