Re: Shortcut to mailboxes screen?
Jeremy Blosser <[EMAIL PROTECTED]> writes: > On Feb 03, Collin Peters [[EMAIL PROTECTED]] wrote: > > macro pager "i" "?" > > macro index "i" "?" > > You shouldn't need the explicit in there, since > will sync anyway. Not immediately, though. Only after you select a mailbox from the list. And the sync won't happen at all if you use C-c to quit Mutt from the browser. Sam
Re: [OT] html email
Rob 'Feztaa' Park <[EMAIL PROTECTED]> writes: > Alas! Alexander Skwar spake thus: > > Well, sure it is - however don't all the HTML capable MUAs convert texts > > like http://this-is-not.a.link.de into a clickable link? Mozilla does. > > Mutt highlights that as a mail, and urlview recognizes it as a link. No > need for HTML-enabled mailers at all. Not clickable, but still a link. It's even clickable if you use Gnome terminal. (I don't.) Sam
Re: char % as quote
David T-G <[EMAIL PROTECTED]> writes: > I seem to be the only one who likes percent, but if I used one of |:}# > then apparently nobody would mind since mutt would already recognize it. Hm. % grep 'quote_regexp\|smiley' .muttrc set quote_regexp="^([ \t]*>)+" set smileys=">From " ;-( Sam
Re: how to change xterm title depending on current mailbox
darren chamberlain <[EMAIL PROTECTED]> writes: > In vim: > > set titleold=My\ Old\ Xterm\ Title > > and it will restore the xterm's title to that string. Yes, but I'd like Vim to restore the XTerm title to whatever it was before I started Vim. This might be something different each time. > -- > I took a speed reading course and read 'War and Peace' in twenty > minutes. It involves Russia. > -- Woody Allen Funny :-)
Mutt IMAP -- how good?
I'm considering switching to IMAP. How good is Mutt as an IMAP client? I'm currently just accessing local mbox files directly, but I'd like to be able to access my mail from other machines. Thanks, Sam
Re: maildir over mbox?
Derek D. Martin <[EMAIL PROTECTED]> writes: > No manager I've ever worked for would tolerate waiting 3 minutes to > open their inbox... That's funny because where I work, we use Lotus Notes, and I'm sure many managers routinely wait this long for Notes to open their inboxes (particularly if they don't replicate). Remarkable what you can get used to, eh? It's always a relief to come home a use a *real* mail client ;-) Sam "OT--Sorry" Padgett
Re: Ispell is too quiet when run from the Compose menu
David T-G <[EMAIL PROTECTED]> writes: > I think the actual flea is that ispell does not follow > $wait_key, myself. I'll buy that. > Who wants to start a movement to get that changed, or submit a > feature patch? I could do the former or the latter, although the latter would require permission from my employer. What is the correct forum for this? mutt-dev? Sam
Re: Ispell is too quiet when run from the Compose menu
Kenneth Pronovici <[EMAIL PROTECTED]> writes: > Ok, I get it. Errors and output disappear so fast that you can't > really see them, which I hadn't noticed before. Doing what I suggested > above would at least let you see that *something* ran, though. Hmm, not > as worthwhile as I thought, sorry. :-( ;-) Thanks for trying. It doesn't bother me now that I know it only means there are no spelling errors. It confused me the first time, though. I brought it up on the list because I suspected another Aspell user at some point would hit this, too, and be confused. I was considering submitting a bug report and wanted to hear what others thought. Sam
Re: Ispell is too quiet when run from the Compose menu
Derek D. Martin <[EMAIL PROTECTED]> writes: > This is part of the Unix philosophy, which goes something like, "if > there's nothing to report, then report nothing." Armed with this > knowledge, there's really no need for such a message... I would amend that to say, "If there's no need to report anything, don't report anything." In this case, there _is_ a need since there's no feedback _whatsoever_ that Ispell ran. This isn't true at the command line: % touch foo % ispell check foo % _ Here you can see that Ispell completed because the shell presented you with a new prompt and a blinking cursor eagerly awaiting input. And if you're really insecure, you can always check the return code with "echo $?". When running Ispell from Mutt, however, you don't have this. You press 'i'. Nothing happens. You press 'i' again. Nothing happens. "Why isn't Ispell running?" you think. "What did I break? Were there no errors, or did it not run?" With the traditional Ispell program, this isn't an issue since it will almost always catch a "misspelling" in one of the headers. With "aspell -e", however, Aspell skips past the message headers. Feedback is an important element of any user interface, GUI or text-based, UNIX or not. Sam [who still thinks this is a flea]
Re: mail being returned
David T-G <[EMAIL PROTECTED]> writes: > To really do it right you should get a domain and have that at your house, > but realistically you could probably use home.explodingnet.com (since > you control the domain and it's your home computer) or nick.yourisp.com > (though that won't show up in a DNS lookup, either) or some such. Services like http://www.dyndns.org> are good for this purpose. Sam
Ispell is too quiet when run from the Compose menu
I sometimes spell check my messages before I send them using Ispell (actually, Aspell), and often I have no errors. When this is the case, however, Mutt does not indicate that the spell checker ran at all! Is there any way I can tell Mutt to display a message, for instance, "Ispell exited with return code 0" or "Spell checking complete"? I suppose I could write a wrapper script for Ispell, but this almost strikes me as a Mutt bug, er, uh, I mean flea. Thoughts? Sam
Re: error sending message
Nick Wilson <[EMAIL PROTECTED]> writes: > Don't know what you mean but I've fixed it. It was a silly error > I'd made. It's just one of those days. Can you tell us what was wrong and how you fixed it (just in case we ever run into the same problem)? Thanks, Sam
signals errors on empty mailboxes?
Why does signal an error when the mailbox is empty? Shouldn't it just be a no-op? The error foils these macros: macro index y "?" macro pager y "?" Thanks, Sam
Re: mailboxes command confusion.
David T-G <[EMAIL PROTECTED]> writes: > Anywhere. Mine happens to be on line 462. Wow. You have a 462+ line .muttrc? Sam [who's impressed]
Re: Mutt sucks less than the rest
mike ledoux <[EMAIL PROTECTED]> writes: > I don't buy into the idea that the editor should be the beginning and > the end of my interaction with the system. I expect a text editor to > be good at editing text--nothing more, nothing less. To insist that > the editor should know the difference between editing email, C source, > or an X pixmap runs counter to the Unix philosophy. This is a complete non-sequitor. Just because my editor recognizes the .c extension doesn't mean it's "the beginning and the end of my interaction with the system". And I don't see how recognizing C source files runs counter to the UNIX philosophy: the editor is still dedicated to editing *text*. > If you really care, I use vi--*not* vim. I'm comfortable with both ed > and ex, but I wouldn't want to use them for email if I could avoid it. Real UNIX users only compose email with ed, no doubt about it! ;-) Sam
Re: Can't send mail from my profile
Nick Wilson <[EMAIL PROTECTED]> writes: > Sounds fine to me Sam, I don't know what VISUAL is though? > I presume it's a config var, I'll go look it up on the manual. Sorry, I think I was unclear: VISUAL is an environment variable. It isn't Mutt-specific. You might want to look at the documentation for your shell for more information. If you use bash, putting export VISUAL=vim in your .bash_profile or .bashrc should set the variable for future sessions. info bash will show take you to the bash documentation. (I'm guessing you use bash since it's the default shell in most GNU/Linux distributions.) If you have VISUAL set in your environment, you shouldn't need to set the Mutt "editor" variable, although it certainly doesn't hurt to do so. > Is that why I sometimes see headers with X-editor: Vim? No, that's actually an extra header people add because they want others to know they use Vim. Sam
Re: Can't send mail from my profile
René Clerc <[EMAIL PROTECTED]> writes: > If you set editor to "", mutt will use the environment variable > EDITOR; make sure this is set (and exported) in your .profile or an > alike file. Wouldn't Mutt actually ignore $EDITOR if $VISUAL is set? Nick, it's probably a good idea to set VISUAL=vim, anyway, since many other applications will then know what editor you prefer. Sam
Re: Mutt sucks less than the rest
Derek D. Martin <[EMAIL PROTECTED]> writes: > Well, that command didn't do much useful for me, Did you try running it after loading post-mode? > To turn it OFF, one would stick this in the appropriate place in > their .emacs file: > > '(post-kill-quoted-sig nil) That line alone does not do anything useful (and looks suspiciously like it's part of a larger `custom-set-variables' declaration). Maybe you mean (setq post-kill-quoted-sig nil) > Easier still (at least if you have xemacs) to go to the > customize menu, and set it there This will of course work ;-) Sam
Re: Bold text
Nick Wilson <[EMAIL PROTECTED]> writes: > I use vim as my editor and can't work out how to make portions of my > text bold? I know many of you use vim so I hope someone can help. Some MUAs will display "a^Ha" (aa) as a bold "a". Is this what you mean? Sam
Re: Mutt sucks less than the rest
Derek D. Martin <[EMAIL PROTECTED]> writes: > Hmmm... well, whenever I reply to a message, everything after > sigdashes is stripped from the message. It's possible that my editor > is doing this (I use post-mode for emacs), and I'll look into that. I'm pretty sure that post-mode does this. You might want to try a command like M-x apropos-variable RET post.*sig RET or somesuch to see what variable enables the behavior. Sam
Re: Recovering interrupted compositions?
Ken Weingold <[EMAIL PROTECTED]> writes: > AFAIK, it is up to the editor, not mutt. When in vim, go to > ':help recover' and it will tell you what you need to know. IOW > you can do it right from within vim. I guess my point is that there are a lot of manual steps here: start new composition, use :recover command in Vim, cut and paste old message into new buffer, etc. Unless there's an easier way? Wouldn't it be nice, though, if Mutt could recognize that it was killed during message composition and allow you to pick up from where you last saved with a simple command, no fuss and muss? Or maybe this isn't quite as easy as I make it out to be? Sam [who promises to never say "no fuss and muss" again]
Re: Recovering interrupted compositions?
Gary Johnson <[EMAIL PROTECTED]> writes: > A better way to handle this is to run screen on your work machine. Then > when your connection drops, simply re-logon to your work machine, run > 'screen -r' to re-attach the screen session, and pick up where you left > off. This is a really good idea. Thanks! Sam
Re: Recovering interrupted compositions?
Ken Weingold <[EMAIL PROTECTED]> writes: > vim -r will give you a list of recoverable temp files. Rarely fails > me. Yes, but then how do I actually send the message. Cut-n-paste into a new composition buffer? I was hoping Mutt had some facility to notice /tmp/mutt-* files that are unsent and allow you to resume composition--something like what Gnus does. If Emacs crashes while you're composing an email in Gnus, the message is automatically stored in a "drafts" group. It then only takes a few keystrokes to get back to exactly where you were. The dropped connections happen often enough for me that cut-n-paste becomes a real nuisance. [ Unfortunately, the real problem--the unreliable network connection--is out of my control :-( ] Thanks, Sam
Recovering interrupted compositions?
I sometimes ssh into my machine from work and use Mutt. The connection through the firewall, however, is, uh, a bit tenuous and often gets dropped. Sometimes this happens when I am composing a message. Is there a good way to recover these compositions and pick up where I left off? I'm using Vim as my editor. Sam
Re: ?'s and hide_missing
Daniel Eisenbud <[EMAIL PROTECTED]> writes: > I mean to get back to some threading loose ends in the next few > days, so I'll add a $hide_missing_parents option, or some such. Terrific! Thanks, Daniel! Sam
?'s and hide_missing
Is there any way to get the Mutt-1.3.24i threading behavior back? It looks like it changed again in Mutt-1.3.25i. Specifically, I like seeing the ?'s, but only enough to give me context. Today, with hide_missing set, I see something like this ?-?-?-?-?-?-?->Re: foo `-?->Re: foo The string of leading ?'s takes up a lot of space and, IMHO, doesn't convey much useful information. Instead, I'd like to see ?->Re: foo `-?->Re: foo This is more compact, but I can still tell how the two messages relate to one another. This used to be the behavior when hide_missing was unset, correct? Is this no longer possible? Thanks! Sam
Re: my-text-mode
Franco Vite <[EMAIL PROTECTED]> writes: > hi mailQuoted1ctermfg=darkcyan > hi mailQuoted2ctermfg=darkgreen > hi mailQuoted3ctermfg=darkred > hi mailQuoted4ctermfg=darkmagenta > hi mailQuoted5ctermfg=darkblue > hi mailQuoted6ctermfg=darkcyan > hi mailQuoted7ctermfg=darkgreen > hi mailQuoted8ctermfg=darkred > hi mailquoted9ctermfg=darkmagenta Ah, with the default colorscheme and a dark background, these are all cyan! Thanks, Sam
Re: my-text-mode
Franco Vite <[EMAIL PROTECTED]> writes: > I use vim, and when I replay I've: > > > blablablabla <= magenta > > >> blablabla <= red > > >>> blablabla <= green Hm. All three lines are the same color for me in Vim. Did you do anything special to get this? > Whit emacs >, >> and >>> are red. post.el might do this: http://astro.utoronto.ca/~reid/mutt/> Sam
Re: my-text-mode
Walt Mankowski <[EMAIL PROTECTED]> writes: > I have > > (turn-on-font-lock) > (global-font-lock-mode t) > (setq font-lock-maximum-decoration t) > > (just to be safe) elsewhere in my .emacs. :-) If you're using GNU Emacs, you only need (global-font-lock-mode 1) The other lines are superfluous. Sam
Re: my-text-mode
giorgian <[EMAIL PROTECTED]> writes:
> i defined the function my-text-mode in my .emacs file, to set all my
> mail editing preferences;
Would be nice to see this function. Do you use `defined-derived-mode'?
> i put in my .muttrc the row:
> set editor="emacs -f my-text-mode"
I think it is better to frob auto-mode-alist in your .emacs:
;; Untested.
(add-to-list 'auto-mode-alist
'("mutt-[a-z]+-[0-9]+-[0-9]+\\'" . my-text-mode))
The just put this in your .muttrc:
set editor=emacs
Does this fix the problem?
Sam [who thinks you might want to look at post.el]
Re: BBDB -> abook?
Thomas Hurst <[EMAIL PROTECTED]> writes: > * Samuel Padgett ([EMAIL PROTECTED]) wrote: > > > Does anyone know of a tool to import records from the Insidious Big > > Brother Database into abook, or am I condemned to do it by hand (my > > penance for using an Emacs-specific address book)? > > Write a bit of lisp to dump it into abook's config format? It's only an > .ini file. Probably wouldn't be too difficult--but I don't even have BBDB installed anymore. > But please do it manually, I believe you should suffer for this > transgression ;) Yes, I must repent. Sam
Re: BBDB -> abook?
Jelmer Vernooij <[EMAIL PROTECTED]> writes: > Try using the lbdb, which has support for bbdb. I'd like to get away from using BBDB in general, however, since it's slow. And I've switched from Gnus to Mutt, so abook probably makes more sense. Thanks, though. Sam
BBDB -> abook?
Does anyone know of a tool to import records from the Insidious Big Brother Database into abook, or am I condemned to do it by hand (my penance for using an Emacs-specific address book)? Thanks! Sam [who apologizes if this is off-topic for this forum]
Re: Quoting when replying
David T-G <[EMAIL PROTECTED]> writes:
> To set my comments apart from others' I started using %_ (the
> common notation for a trailing space, just like the From_
> header). I had, IIRC, already seen a few folks using | and
> within a few years all manner of quoting (most commonly : :_ |
> |_ $ but occasionally % and %_ just like me) abounded.
These prefixes all make refilling paragraphs difficult in Vim.
> I've simply kept it since then, and it's relatively unique and
> still recognizable.
Relatively unique is _bad_ for a quote character! ;-)
> Hey, at least mine is easy to match with $quote_regexp!
Yes, but I choose not to since I detest false positives. ('%'
functions as a comment character in many places.) This is the
same reason I don't keep ':' and '}' in $quote_regexp.
Sam
--
A whole population of identical-looking human beings? This chilling
dystopian vision has already come to pass in the fall J. Crew catalog.
Re: A couple of probably dumb questions :)
Will Yardley <[EMAIL PROTECTED]> writes: > you can do the exact same thing with a simple procmail recipe. Nifty. > it can be argued (and as the gnus manual points out) that this > might be unreliable. Yeah. The manual goes on to give this tip: Here's a neat feature: If you know that the recipient reads her mail with Gnus, and that she has `nnmail-treat-duplicates' set to `delete', you can send her as many insults as you like, just by using a `Message-ID' of a mail that you know that she's already received. Think of all the fun! She'll never see any of it! Whee! > you can save them to a separate folder rather than deleting them > outright if you're paranoid. Yes, Gnus will do this, too. > i imagine you could easily use procmail to do something similar > to what gnus does as well (ie marking it as read)... Well, Gnus doesn't show you read messages by default--like a newsreader. And, depending on how you've set things up, you can make the messages expire after a certain amount of time. So, after say a week, it would be deleted, and you'll never have seen it. If you're a Mutt user, however, the procmail approach looks like the way to go. Sam -- It doesn't matter if you're the greatest guitar player in the world. If you're not enlightened, forget it. -- George Harrison
Re: A couple of probably dumb questions :)
Thomas Hurst <[EMAIL PROTECTED]> writes: > I had a look at Gnus too, mainly because people seem to think it handles > things like [crap] in subjects an dupes really well; >From the Gnus manual: Duplicate suppression is not a very subtle instrument. It's more like a sledge hammer than anything else. It works in a very simple fashion--if you have marked an article as read, it adds this Message-ID to a cache. The next time it sees this Message-ID, it will mark the article as read with the `M' mark. It doesn't care what group it saw the article in. > something I'm interested in being handled well somewhere between > fetchmail and mutt. I wouldn't recommend trying to use Gnus split methods without using Gnus as your MUA or newsreader. Running an instance of Emacs just to sort your mail is not the best use of system resources ;-) Also, from what I can gather, Gnus suppresses duplicates when you enter a group, not during mail splitting. Having said that, if you do use Gnus to read mail or news, you simply have to frob a variable or two, and you'll never see a duplicate again... Sam -- It doesn't matter if you're the greatest guitar player in the world. If you're not enlightened, forget it. -- George Harrison
Re: Quitting Mutt from Browser
Kenneth Pronovici <[EMAIL PROTECTED]> writes: > What about CTRL-C...? Seems to work everywhere... If I delete a message in a mailbox, type "c ?", then quit with "C-c", Mutt doesn't purge the deleted message :-( Sam -- It doesn't matter if you're the greatest guitar player in the world. If you're not enlightened, forget it. -- George Harrison
Re: Quitting Mutt from Browser
Ken Weingold <[EMAIL PROTECTED]> writes: > Or you could just remap 'q' to Quit. Or use 'Q'. Key is not bound. Press '?' for help. Hm. Sam -- It doesn't matter if you're the greatest guitar player in the world. If you're not enlightened, forget it. -- George Harrison
Quitting Mutt from Browser
Is there a way to exit Mutt directly from the browser? After "c ", "q" just takes me back to the "Open mailbox" prompt. The help doesn't reveal any other promising commands. I'm running Mutt 1.3.24i and have "quit" set to "yes". Thanks, Sam -- It doesn't matter if you're the greatest guitar player in the world. If you're not enlightened, forget it. -- George Harrison
Re: mail-followup-to standard....
Will Yardley <[EMAIL PROTECTED]> writes: > Ren? Clerc wrote: > >> Then you probably have set ignore_list_reply_to=yes (where no = default) > > i don't. > > zugzug [~]% grep -ri ignore_list_reply .mutt* > zugzug [~]% A better test might be :set ?ignore_list_reply_to inside of Mutt. > yes i agree, but sometimes _other_ people set MFT improperly (or even > more likely, cc someone improperly). since people who are already set > to receive followups are then included in YOUR MFT header, people who > are actually on the list may end up getting ccd by everyone else. Mutt should generate the MFT header based on the people you've included in the To: and Cc: headers. If you remove the improperly Cc-ed individual from the Cc: header, Mutt should not put that person in the MFT header. Sam
Re: Mail-Followup-To
Thomas Hurst <[EMAIL PROTECTED]> writes: > * Samuel Padgett ([EMAIL PROTECTED]) wrote: > > > But won't people who aren't subscribed to the lists not receive your > > messages? > > A rare special case, especially since the majority of the lists I'm > on don't even allow external posts. I subscribe to several lists (some bug reporting lists and developer lists) where it's very common for people who aren't subscribed to send messages to the list. Of course, list reply certain makes sense for lists that don't allow external posts. > I'd rather one person with questionable reasons posting to the > list not receive a message than 4 people receive two each. I always figured that, if it really annoys them, they should switch to an MUA that generates a Mail-Followup-To header (like Mutt) or one that handles duplicates really well (like Gnus). Sam
Re: Mail-Followup-To
Thomas Hurst <[EMAIL PROTECTED]> writes: > * Thorsten Haude ([EMAIL PROTECTED]) wrote: > > > Yeah, the basic brain-dead-mailer-problem and its reply-to-munging or > > group-reply answer. Fortunately, there's Mutt. I use group-reply about > > once a year. > > I have 'r' rebound to list-reply for all my mailing lists (bar one > broken one). Nice having a MUA this flexible, means all the lists that > use (or don't use) Reply-To: act the same :) But won't people who aren't subscribed to the lists not receive your messages? Sam
Re: mbox Postmark Line vs. Message Date Header?
Vineet Kumar <[EMAIL PROTECTED]> writes: > > * Samuel Padgett ([EMAIL PROTECTED]) wrote: > > > > > So the advantage of Maildir is speed, and the disadvantage > > > is that it eats inodes for breakfast? > > This is my experience, yes. Another advantage is peace of mind > that you'll never again fall prey to a corrupted mailbox due to > a delivery occurring at the wrong time. But shouldn't well-behaved MTAs and MUAs perform locking that prevents this from happening? Sam
Re: mbox Postmark Line vs. Message Date Header?
David T-G <[EMAIL PROTECTED]> writes: > ...and then Samuel Padgett said... > % Mutt seems to use the values out of the Sender header and the Date > % header to construct the From_ line. So maybe the solution is the > > Makes sense -- if it's there. I just checked another message to see and > there was no Sender: header. It's new to me, though I did a quick grep > on my spoolfile and found quite a few right off. I think Gnus uses Sender: to check whether you should be allowed to cancel a Usenet post. But that should go away now that they've added cancel locks. > % roundabout nnml -> mbox using Gnus, then mbox -> Maildir -> mbox > % using Mutt. Hm. That's a lot of work. > > With tagging it should be easy, right? Well, OK, Mutt will do most of the work--but it's still a lot of work ;-) > % Or perhaps I should just switch to Maildir. > > I hear that that's almost always a fantastic idea. I personally have > been too lazy :-) So the advantage of Maildir is speed, and the disadvantage is that it eats inodes for breakfast? Maybe I should switch to a journaling filesystem as well. Sam
Re: mbox Postmark Line vs. Message Date Header?
David T-G <[EMAIL PROTECTED]> writes: > ...and then Samuel Padgett said... > % It seems Gnus reads MMDF, but doesn't write it. Gnus does IMAP, > > Ahhh... It reads anything and writes only its own (well, OK, mbox); > urgh. Actually, Gnus writes a bunch of stuff: mbox, IMAP, nnml, babyl, MH spool, NNTP, maybe more? > Interesting. I suppose the acid test would be to let mutt convert a > Maildir to an mbox and see what it does :-) Mutt seems to use the values out of the Sender header and the Date header to construct the From_ line. So maybe the solution is the roundabout nnml -> mbox using Gnus, then mbox -> Maildir -> mbox using Mutt. Hm. That's a lot of work. Or perhaps I should just switch to Maildir. Sam
Re: mbox Postmark Line vs. Message Date Header?
David T-G <[EMAIL PROTECTED]> writes: > ...and then Samuel Padgett said... > % Hm. Gnus reads Maildir, but doesn't write it (although I think > % they're working on this). Maybe I can grab a development version. > > Can it write MMDF or save to an IMAP server, both of which mutt also > speaks fluently? It seems Gnus reads MMDF, but doesn't write it. Gnus does IMAP, though. But then I'd have to set up an IMAP server :-| > It seems to me, though it's probably no help to you, that it's > Gnus that's doing it wrong; Possible, although Gnus tends to be a very well-behaved MUA. Maybe I should ask in a Gnus forum? By the way, I was curious about what slrn does when I use "o" to save an article: in the From_ line, it uses the address out of the >From header, but does _not_ use the date out of the Date header. Instead, like Gnus, it uses the date the message is being saved. > I admit, though, that mutt probably oughta display the Date: > info instead of the From_ info regardless of whether or not the > latter is accurate. Yes, I think so. FWIW, Gnus uses the Date header when it constructs its summary buffer. Sam
Re: mbox Postmark Line vs. Message Date Header?
David T-G <[EMAIL PROTECTED]> writes: > Since there was no From_ header before, Gnus had to make one up > somehow. Makes sense. > Can you export to Maildir instead? You could then read that in > with mutt and save to mbox. Hm. Gnus reads Maildir, but doesn't write it (although I think they're working on this). Maybe I can grab a development version. Even if I did this, wouldn't Mutt have the same problem Gnus had: no From_ header? > % > How does the From: header for this representative message look? > % > % Um, let's see... > % > % From: Samuel Padgett <[EMAIL PROTECTED]> > > Oh, *duh* Sorry. How about the Date: header instead? :-) Sure ;-) Date: Sun, 11 Nov 2001 00:40:32 -0500 > What happens if you sort by date? Do they order themselves > correctly? They seem to. So Mutt groks the Date header, but isn't displaying that date in the index. Maybe Mutt uses the From_ header instead for efficiency? Sam
Re: mbox Postmark Line vs. Message Date Header?
David T-G <[EMAIL PROTECTED]> writes: > ...and then Samuel Padgett said... > % I recently moved some messages that I was reading with another MUA > % to an mbox file I read with Mutt. I noticed that in the index > > How did you move them? What's the other MUA's format? [What's the other > MUA?] I moved them using the C-o command in Gnus. The messages were previously stored in the nnml format. nnml is a Gnus-specific format that stores each message in its own file, a little like Maildir. > % Mutt shows the date I moved the messages, not the date each > % message was sent. I looked more closely at the mbox file and saw > % that the postmark lines for these messages read something like > % > % >From nobody Sun Nov 25 23:28:45 2001 > > How does the From: header for this representative message look? Um, let's see... From: Samuel Padgett <[EMAIL PROTECTED]> > Are you sorting by date, threads, received, or none? Threads. Sam
mbox Postmark Line vs. Message Date Header?
I recently moved some messages that I was reading with another MUA to an mbox file I read with Mutt. I noticed that in the index Mutt shows the date I moved the messages, not the date each message was sent. I looked more closely at the mbox file and saw that the postmark lines for these messages read something like >From nobody Sun Nov 25 23:28:45 2001 It seems Mutt is using this date and not the date in the Date header. I would like to see the true date of the message in the index, however. Is there a way to do this? Thanks, Sam
Re: line length
Vincent Lefevre <[EMAIL PROTECTED]> writes: > If you want to reformat quoted text, emacs is quite bad at this, > and I've never found *perfect* LISP code to do that. :( Huh? Emacs is _excellent_ at this. What mode and you using to edit messages and what problems are you having? Sam [writing this in Vim]
Re: line length
Will Yardley <[EMAIL PROTECTED]> writes: > mutt doesn't have an editor, so this is a function of your editor. in > vim you can use :set tw=74 or :set textwidth=74 In Emacs, (add-hook 'text-mode-hook 'turn-on-auto-fill) This assumes you're using text-mode or one of its derivatives to compose messages. > nvi and other vi clones should be the same, but you can't use 'gqip' or > 'gqap' to format lines (maybe install par). M-q in Emacs. > if you use emacs, i'm sorry, and YOU are on your own :> ;-) Sam
