Re: japanese with devel mutt
On Sun, Nov 12, 2000 at 04:36:37PM +0800, Anthony Liu wrote: OK here is my take: There are two xterms you can choose to display Japanese character set. However I have only tried the more popular shift-jis encoding, which the other one is deprecated, I think. One is Kanjiterm, Kterm in short. However, it is a bit hard to find. The other one is Aterm, which is called the Afterstep Term. You have to compile Aterm with somthing like "--enable-kanji" with configure. Once you have it compiled. Start Aterm, fire up lynx and load the page "http://www.yahoo.co.jp/". Notice: lynx support for Japanese and Chinese encoding is a bit broken. Enlightened Term (Eterm) said to support Kanji (which is a bad description), I have yet to get it to work, you might need to set the locale variables. However, if you use emacs, you should try out MULE, which is a multi-lingual edition for emacs. If you want X apps to display Japanese, there are more you have to do then just the xterm. This isn't my problem. I'm using rxvt built with kanji support -- the problem is that mutt only displays the characters properly if I set the LANG environment variable. kanji support is working great in the term, I just need to convince mutt to display it properly. Perhaps I'll try rebuilding xterm with unicode support :) ttyl, -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
character sets
I'm trying to figure out how to display diacritical marks in my received
emails. I've tried setting LC_CTYPE as suggested in the FAQ; that leads
to the error message `couldn't set locale correctly'. I've read about
`charset' and `charset-hook' in the manual, but what do I actually *do*
in my .muttrc to get a better character set? (Something like PC-850
charset would be fine).
PS: I installed charmaps-0.0.tar.gz prior to building mutt.
--
TIA/jtw
% mutt -v
Mutt 1.2.5i (2000-07-28)
Copyright (C) 1996-2000 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: SunOS 5.7
Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK
+USE_IMAP -USE_GSS -USE_SSL -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX
+HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS
SENDMAIL="/usr/lib/sendmail"
MAILPATH="{darwin.sfbr.org}/var/mail"
SHAREDIR="/home/jeffw/gnu2/share/mutt"
SYSCONFDIR="/home/jeffw/gnu2/etc"
-ISPELL
To contact the developers, please mail to [EMAIL PROTECTED].
To report a bug, please use the muttbug utility.
Re: N in folder list
On Thu, 09 Nov 2000, Mike E wrote: Keeping my .muttrc up to date is starting to be a hassle. I guess that's what I get for being on dozens of mailing lists. :) No, the reason to be on dozens of mailing lists is to give you work to do on your .muttrc to keep it up to date. :-) -- Greg MathesonLanguage learning/teaching Chinmin College, is like hitting head against brick wall. Taiwan Feels good when over
mailing list handling
Hi again. I like mutt's ability to set the Mail-Followup-To variable, and the list-reply functionality, but I don't like how it shows the list name instead of the person who sent the mail in the index view. I already have procmail sort mail into seperate mailboxes, so I know what mailing list I'm dealing with. What's the proper way to keep the default behavior, but still use the additional handy features you get when using the subscribe command. Thanks, -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Re: mailing list handling
On Mon, Nov 13, 2000 at 01:28:12PM -0500, Josh Huber wrote: I like mutt's ability to set the Mail-Followup-To variable, and the list-reply functionality, but I don't like how it shows the list name instead of the person who sent the mail in the index view. I already have procmail sort mail into seperate mailboxes, so I know what mailing list I'm dealing with. What's the proper way to keep the default behavior, but still use the additional handy features you get when using the subscribe command. From my .muttrc: set index_format = "%4C %Z %[%b %d] %-15.15n (%4l) %s" The default format string has "%-15.15L" instead of "%-15.15n". The "n" expands to the author's real name (or address if the real name isn't known). I believe the numbers have to do with the field length. -- Luke
Re: mailing list handling
On Mon, Nov 13, 2000 at 11:49:33AM -0800, Luke Ravitch wrote: set index_format = "%4C %Z %[%b %d] %-15.15n (%4l) %s" The default format string has "%-15.15L" instead of "%-15.15n". The "n" expands to the author's real name (or address if the real name isn't known). I believe the numbers have to do with the field length. Yep, ok. Thanks. -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Re: mailing list handling
Ben Reser [EMAIL PROTECTED] wrote on Mon, 13 Nov 2000: FYI using that will break your outbox (if you use one) showing who the outbound mail is to. So I'd use it like this: folder-hook . 'set index_format = "%4C %Z %[%b %d] %-15.15n (%4l) %s"' # Set the outbox index different, I want to see who I'm sending to. folder-hook out 'set index_format = "%4C %Z %[%b %d] %-15.15L (%4l) %s"' That's why I prefer the %F expando; it saves from having to use these two hooks, while the net result is still essentially the same. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com / // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / There is nothing in the world stronger than gentleness.
Re: mailing list handling
Josh Huber [EMAIL PROTECTED] wrote on Mon, 13 Nov 2000: What's the proper way to keep the default behavior, but still use the additional handy features you get when using the subscribe command. Change your $index_format. Changing the %L into a %F in the format string will likely make you happy. If not, check the manual's entry for the variable for more information. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com / // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Microsoft Windows... a virus with mouse support.
Re: mutt New Mail Notifications.
Marco Ahrendt [EMAIL PROTECTED] wrote on Tue, 14 Nov 2000: whenever i get new mail this N mark is correctly set by mutt. the interesting thing is, when i read my mail in the mailbox and i mark it "new" by hand again (after reading it) the mail gets the N flag fine. but after changing the mailbox and listing all mailboxes, the mailbox which stores the mail with N flag doesn´t has the N flag self. very complicated eh?! :) This is because Mutt doesn't update the folder modification/access times according to whether the folder still has new mail in it (or not). For mbox folders, the N appears in the folder listing if (and only if) the modification time for the file is newer than the access time. After you've entered a folder with Mutt, even if you don't touch the contents in any way (read any messages or anything), the access time will be updated. And if you do change something in the folder, once it's written to the disk the modification and access times will be set to the same time, and the folder will not be considered to contain any new mail (regardless of individual message states inside). This issue has come up before, and I have some vague memories about a patch that would set the file access time to 1 second before the file modification time when an mbox folder was exited, if it contained new mails. But I'm not sure if that's just me imagining things, or not. Regards, Mikko (who prefers Maildir as a folder-format for incoming mails -- among other things, no hassles with the "folder has new mail" detection) -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com / // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / "I took an IQ test and the results were negative."
Folder specific index_format
Hello, I'm attempting to use the following (which seem logical enough for me) to perform folder specific index formatting: folder-hook . \ 'set index_format="%4C %4N %Z %[!%y%m%d-%H%M] %-17.17F (%5l) %s"' folder-hook in-l-bugtraq \ 'set index_format="%4C %4N %Z %[!%y%m%d] %-14.14F (%5l) %s"' However, they don't work. I get an error: %4N: unknown variable Does anyone have a better way of formatting indexes per folder? cheers, -- iain truskett, aka Koschei.http://eh.org/~koschei/ "Steve Maguire's /Writing Solid Code/ (Microsoft Press, 1993) and Steve McConnell's /Code Complete/ (Microsoft Press, 1993) both have much good advice on debugging. --- Kernighan and Pike, "The Practice of Programming"
Re: mutt New Mail Notifications.
On Tue, Nov 14, 2000 at 01:45:10AM +0200, Mikko Hänninen wrote: # # This issue has come up before, and I have some vague memories about a # patch that would set the file access time to 1 second before the file # modification time when an mbox folder was exited, if it contained new # mails. But I'm not sure if that's just me imagining things, or not. For what it's worth, (ie, I'm not sure if this would solve his problem) I build mutt with the "--enable-buffy-size" option. This has mutt check the file size of the folder instead of the access time of the folder. This provides me with a reliable indication of when the folder has new mail. YMMV. -greg
Re: mutt New Mail Notifications.
On Tue, Nov 14, 2000 at 01:45:10AM +0200, Mikko Hänninen wrote: This is because Mutt doesn't update the folder modification/access times according to whether the folder still has new mail in it (or not). For mbox folders, the N appears in the folder listing if (and only if) the modification time for the file is newer than the access time. After you've entered a folder with Mutt, even if you don't touch the contents in any way (read any messages or anything), the access time will be updated. And if you do change something in the folder, once it's written to the disk the modification and access times will be set to the same time, and the folder will not be considered to contain any new mail (regardless of individual message states inside). This issue has come up before, and I have some vague memories about a patch that would set the file access time to 1 second before the file modification time when an mbox folder was exited, if it contained new mails. But I'm not sure if that's just me imagining things, or not. Here's a good reason to use maildir's. Do the following: unset mark_old and use maildir's and you'll get the behavior you desire. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org Maslow's Maxim: If the only tool you have is a hammer, you treat everything like a nail.
Re: mailing list handling
On Mon, Nov 13, 2000 at 01:28:12PM -0500, Josh Huber wrote: What's the proper way to keep the default behavior, but still use the additional handy features you get when using the subscribe command. you want to change your default $index_format to use %F instead of %Z, most likely. me
procmail and mutt New Mail Notifications.
Hi! I'm using mutt and procmail. It's an older version of procmail that didn't natively support maildirs, and so at the time I'd found a program called safecat, that came with a binary that could be used with procmail to move mail safely into a Maildir. I've noticed that I filter mail successfully into at least 6 mailboxes, and I have my ~/Maildir/ as well as 5 other mailboxes in a seperate ~/Mail/* tree configured in my .muttrc. Problem is, mutt never tells me that I have new mail in any of the other mailboxes except for Maildir. But if I'm in one of the other mailboxes, and I get new mail, mutt immediately tells me that I have new mail in ~/Maildir. Is this because the program I'm using to move my mail to my maildirs is not properly setting some kind of date/time stamp? Would a newer version of procmail do better? or does mutt just not tell you when you have new mail in other folders, except for ~/Maildir? -- Adrian Chung Software Engineer e-smith, Inc. [EMAIL PROTECTED]+1 613 564 8000x4379888 ESMITH 1 Suite 1500, 150 Metcalfe St, Ottawa, ON, K2P 1P1, Canada www.e-smith.com (corporate) | www.e-smith.org (development)
Re: procmail and mutt New Mail Notifications.
On Tue, Nov 14, 2000 at 12:22:16AM +0200, Mikko Hänninen wrote: Adrian Chung [EMAIL PROTECTED] wrote on Mon, 13 Nov 2000: or does mutt just not tell you when you have new mail in other folders, except for ~/Maildir? That's the default. If you have other incoming mail folders, you need to tell Mutt about them. This is done with the "mailboxes" command. In your .muttrc: mailboxes ~/Mail/folder1 ~/Mail/folder2 ... (or possibly =folder1, =folder2, if your $folder points to ~/Mail) So should this work: mailboxes ~/Maildir mailboxes =DevInfo mailboxes =GeneralDiscussion mailboxes =AdvancedForum mailboxes =CustomerForum mailboxes =NewUserForum mailboxes =WishList Or does it all need to be on one line? To further clarify, I should ask... Does mutt actually tell you when you have mail in other mailboxes? Or only the Maildir? In other words, is it my setup that's broken? -- Adrian Chung Software Engineer e-smith, Inc. [EMAIL PROTECTED]+1 613 564 8000x4379888 ESMITH 1 Suite 1500, 150 Metcalfe St, Ottawa, ON, K2P 1P1, Canada www.e-smith.com (corporate) | www.e-smith.org (development)
Re: mutt New Mail Notifications.
hi all, when discussing the new mail mark problem i have a question too. whenever i get new mail this N mark is correctly set by mutt. the interesting thing is, when i read my mail in the mailbox and i mark it "new" by hand again (after reading it) the mail gets the N flag fine. but after changing the mailbox and listing all mailboxes, the mailbox which stores the mail with N flag doesn´t has the N flag self. very complicated eh?! :) to sum up, mutt doesn´t recognizes a N flag in any mail of mailbox X and only show´s the N flag after fetching mail and open the box at the first time. any ideas? cya Marco -- adconsys AG, Karl-Liebknecht-Str. 19, 04107 Leipzig Tel.: 0341-98 474 0 / Fax: 0341-98 474 59 E-Mail: [EMAIL PROTECTED] URL: www.adconsys.de Key Fingerprint: AE02 AA7E CFD1 0A4C 497D 8526 E495 102B A624 3C99
Re: procmail and mutt New Mail Notifications.
Adrian Chung [EMAIL PROTECTED] wrote on Mon, 13 Nov 2000: So should this work: mailboxes ~/Maildir mailboxes =DevInfo snip Yes, that shoudl work. To further clarify, I should ask... Does mutt actually tell you when you have mail in other mailboxes? Or only the Maildir? In other words, is it my setup that's broken? The folder format doesn't matter, Mutt checks all kinds of folders (that it is able to recognise, anyway) for new mail, if you've specified the folders in a mailboxes line. If you're using mbox (regular mailbox format) and you don't get new mail notification despite marking the folders with "mailboxes", then you're probably running into the oft-asked "Why doesn't Mutt mark my mbox folder containing new mail?" issue. The answer is that for some reason the mbox folder timestamps are not set correctly, and Mutt doesn't detect the new mail because of that. As to the reason behind that, it could be any number of things. Check the archives. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com / // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / For a reply, send a self-abused stomped antelope to [EMAIL PROTECTED]
