Re: short-keys
On 18 Jun 2008 21:26 -0700, by [EMAIL PROTECTED] (Ravi Uday): > Does anyone has a comprehensive list of short cut keys while > navigating/composing/deleting mails when using mutt 1.5.17 For composing, you will have to refer to the help for your editor of choice. As long as you are within mutt, however, you can always press `?' to get a list of the currently bound keys and their functions. This can easily be copied and pasted into another document that you can print and put up on the wall (or wherever else strikes your fancy). -- Michael Kjörling .. [EMAIL PROTECTED] .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP key ID: 0x 758F8749 BDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Re: A mutt flea, or just me?: Last reply paragraph is not
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, June 18 at 07:16 PM, quoth Erik Christiansen: > However, invoking vim within mutt reveals the invisible last (or > only) paragraph. Curiously, appending a newline, to terminate the > last line, while in vim, causes the whole trailing paragraph to also > appear on exit to mutt. Come to think of it, how can such an email actually exist? When email is transmitted via SMTP, it's *required* to be terminated by a newline. If it isn't, there's no way to know that the message has finished. So, if you're getting a message delivered to you that's missing a terminating newline, that suggests to me that some part of your message delivery service is snipping off the newline. ~Kyle - -- How can you expect to enjoy life without heartily disliking a good many people? -- Cary Tennis -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkhacqMACgkQBkIOoMqOI15liQCg/khgMON0N98U7DN7rjzytfHj ZP4AoJ7k/VDfUu7tnT7E9FtWippsbqzt =ruIt -END PGP SIGNATURE-
Re: ":source ~/.muttrc" command weirdly moves message around in
On Tue 06/17/08 at 02:30 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > 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. I've never actually once ever had any matching I didn't want on <|cv|dm in the line folder-hook '<|cv|dm''set index_format="%3C %Z %[%m/%d] %-22.22F \ %?l?%4l&%4c? %s"' The "cv" and "dm" folders don't ever get mail sent directly to them. The only way any messages ever get into them is when I save them to there from my inbox, and messages I *send* to the persons (whose initials those are) get saved to there instead of to my "sent-mail" folder. Given that, do I still need to be concerned about false matches? I would think there's nothing that could ever get erroneously matched to them. -- // [EMAIL PROTECTED] // It is only when we step away from the actual and begin to explore the possible that life's infinities begin to reveal themselves to us. -- James Kent pgpEyfqITIGpX.pgp Description: PGP signature
Re: short-keys [OT}
> 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. I find these hysterics hysterical -- some bureaucrat's idea of something IMPORTANT to put at the end of the outgoing e-mail of every single person in a company. Nobody cares about your dumb disclaimer, you rube. Of course, none of this is alex's fault. Most companies, in fact, have one that's even longer and more pompous. -- // [EMAIL PROTECTED] //
