vi-style keybindings for mutt
All, I figure this question has been asked before, but I can't find it anywhere. Is there any way to switch the key-bindings while line-editing (like at the 'To:' prompt or at any other prompt that *mutt* brings up) to simple vi-style key bindings (I'm thinking of a patch here)? Much like you expect after typing 'set -o vi' at a Posix-sh prompt. Thanks... /db
Re: iso-2022-jp in headers
Hello Sam, On Tuesday, August 6, 2002 at 9:41:16 AM -0700, Sam Peterson wrote: The trouble is that her name is written in Japanese in the from header in what I believe is iso-2022-jp, as that's the content-type of her message. The CT of the message is the type of the *body*. The headers as the From: have to declare their own individual charset and encoding, something as From: =?iso-2022-jp?b?something?= you don't see in Mutt because it decodes it for you, but can see raw by piping it to less. If it's not the case, and Japanese chars are unencoded, then that's a problem in her mailer. Should not be. When she's attributed, her name comes out like this: ?$BF#AR ?$BD;R, in the body, and in the To: header [...] If I switch my locale to ja_JP and look in my sent-mail in a kterm, the name appears to not have been encoded correctly, as it still shows up as gibberish. Yes: 2022 gets decoded, converted to $charset, chars not existing are changed to question marks (the ESCs in your example), and the bytes go straight to terminal. As terminal is Latin-1, you don't see Japanese, but the bytes that would be Japanese on a Japanese terminal. When you end composing your reply, Mutt believes all these bytes are Latin-1 chars, as that's what $charset says about your terminal. Sorry, don't think I'm clear, but that's normal in Mutt's design. Said in another way: Unlike MSOE, Mutt has not the memory of the charset of the message you reply to... From:, attribution and quotings are converted to $charset, possibly losing information. And you are in that case. I believe the only solution is to have a terminal with more capabilities, so the conversion doesn't lose anything. In your case 2022 or Unicode. And set $charset and LC_CTYPE accordingly. [ja_JP in kterm] that's a little inconvenient though, as the modelines and menubar show up in Japanese and when I try composing other messages my language setting in Emacs defaults to Japanese I believe Mutt only needs $charset and LC_CTYPE to describe terminal. So you could play with something as: | export LANG=en_US.ISO8859-1 | export LC_CTYPE=ja_JP ...to have menus talking English but mails in Japanese. If this doesn't work properly, try the other way round: | export LANG=ja_JP | export LC_MESSAGES=en_US.ISO8859-1 ...or variations of this, as far as LC_CTYPE is explicitly or implicitly set to ja_JP. tried numerous things such as playing with [...] $locale $locale is only for the date and time. Bye!Alain. -- Microsoft Outlook Express users concerned about readability: For much better viewing quotes in your messages, check the little freeware program OE-QuoteFix by Dominik Jain on URL:http://flash.to/oblivion/. It'll change your life. :-) Now exists also for Outlook.
Re: Content-Type: APPLICATION/ZIP
At Wed, Aug 14 2002 [14:18 -0700], Deb aroused my curiosity with: Any ideas about why my mailcap didn't work? See section 5.4 MIME Autoview in the mutt manual. Tschoe, Steff
Re: vi-style keybindings for mutt
* David Britton [EMAIL PROTECTED] [2002-08-15 06:30]: I figure this question has been asked before, but I can't find it anywhere. Is there any way to switch the key-bindings while line-editing (like at the 'To:' prompt or at any other prompt that *mutt* brings up) to simple vi-style key bindings (I'm thinking of a patch here)? Much like you expect after typing 'set -o vi' at a Posix-sh prompt. no. send the patch! i hope you are aware that there is a lot to be changed to achieve vi modes there? may i remind you of the find commands (fFtT), replace mode, and the undo command? Sven
Correcting bad From formats
--4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, The following bad From formats are displayed with F flag in my index as if they were from me (andre): From: Luca Riazzi LRIAZZIremoveme-cancellami@writeme.com From: Neil Tisdale neil.discard[EMAIL PROTECTED] From: lst_cwby mailto:l_@m_@st_@n_@__c_@wb_@y@@bt_@nt_@[EMAIL PROTECTED]@m Can I work around this somehow? -Andre --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9W74sWkhBtALlJZ0RAlWqAJ9XAQfkREmwLm5itQt+/bu4YZJktgCgmdUS P9av9sgfhcHvpilVkUwv8Ns= =dwgZ -END PGP SIGNATURE- --4SFOXa2GPu3tIq4H--
Running Mutt from a setgid program
We're having a problem running mutt from a program that is running setgid. Mutt produces the following error: mutt: I don't want to run with privileges! Everything is fine if we just run mutt from the command line, but we need to call it from within another program which is running setgid. Anyone know of a workaround for this one? -- Al Weston [EMAIL PROTECTED]
Re: Running Mutt from a setgid program
Hi,
* Al Weston [02-08-15 17:08:19 +0200] wrote:
We're having a problem running mutt from a program that is
running setgid. Mutt produces the following error: mutt:
I don't want to run with privileges!
Clear. Just use the source and comment the check out (in
main() in main.c).
,[ ~/tmp/builds/mutt/main.c ]-
| [...]
| /* sanity check against stupid administrators */
|
| if(getegid() != getgid())
| {
| fprintf(stderr, %s: I don't want to run with privileges!n,
| argv[0]);
| exit(1);
| }
| [...]
`-
bye, Rocco
Re: Multiple attachment script
On 14/08/02, from the brain of Gary Johnson tumbled: On Wed, Aug 14, 2002 at 05:38:41PM -0700, Michael Montagne wrote: I'm playing around a bit with rox. There is a feature called Send-to. It will take a selection of files and pass them to a program. What I'd like is to pass the files to mutt and have them be the attachments. I tried: konsole -e mutt -a $@ in a shell script but it appears that the -a argument only accepts one file, cause it works then. Is my desire possible? Well it must be, but is it possible within reasonable limited shell script programming knowledge? How about this? cmd=konsole -e mutt for a in $@ do cmd=$cmd -a $a done $cmd HTH, Gary Good idea. Here's another one. #!/bin/bash if [ $# -eq 1 ] then konsole -e mutt -a $1 else tar -czf ~/attachedfiles.tgz $@ konsole -e mutt -a ~/attachedfiles.tgz fi -- Michael Montagne [[EMAIL PROTECTED]] 503.226.1575 --
Re: vi-style keybindings for mutt
On Thu, Aug 15, 2002 at 03:57:52PM +0200, Sven Guckes wrote: * David Britton [EMAIL PROTECTED] [2002-08-15 06:30]: Is there any way to switch the key-bindings while line-editing (like at the 'To:' prompt or at any other prompt that *mutt* brings up) to simple vi-style key bindings (I'm thinking of a patch here)? no. That's unfortunate. send the patch! Well, I doubt it, but we will see. i hope you are aware that there is a lot to be changed to achieve vi modes there? Oh, I have a feeling it's more difficult than I want it to be, but I would like the change (I hit esc just about every time I go to edit a string in mutt). Since I hardly ever use the arrow keys anywhere else, it'd be nice if mutt could be taken off the short list. /db
Re: Content-Type: APPLICATION/ZIP
Stefan Frank [EMAIL PROTECTED] had this to say, At Wed, Aug 14 2002 [14:18 -0700], Deb aroused my curiosity with: Any ideas about why my mailcap didn't work? See section 5.4 MIME Autoview in the mutt manual. Thanks for the pointer. I'll check it out! deb -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- There are 010 types of people in the world: those that understand binary, and those that don't. ô¿ô ~
new random sig in emacs - how?
Well age is catching up with me I think as suddenly today I can't seem to recall (or find on the web or in the manual) the keystrokes required to pull a new signature into emacs; can someone enlighten me? Here are the facts: I'm using randsig3.pl (and *not* post.el) to randomly pull a sig into each of my messages. If the random sig didn't really fit the occassion or person, I used to be able to issue a keystroke (or two? sigh) and it would go out and insert a new random sig (i.e. it would call randsig3 again and replace the old sig with a new one from my quote collection file). Can anyone enlighten this absent-minded professor? I promise I'll write it down this time. Thanks. dan -- Dan Resleremail: [EMAIL PROTECTED] Computer Science Dept. Virginia Commonwealth University Richmond, VA 23284-3068 USA
auto_view with mutt in Cygwin?
I can't seem to figure out how to get mutt to dump html to lynx (or links) in Cygwin. I have the same setting I have on my FreeBSD box, but Mutt says: mailcap entry for type text/html not found for any html mail I get? ...and yet I have a text/html entry in my ~/.mailcap file. Anyone using mutt under Cygwin that has figured this out? -- Sean LeBlanc:[EMAIL PROTECTED] I hope I never get so old I get religious. -Ingmar Bergman
new random sig in emacs - how?
Well age is catching up with me I think as suddenly today I can't seem to recall (or find on the web or in the manual) the keystrokes required to pull a new signature into emacs; can someone enlighten me? Here are the facts: I'm using randsig3.pl (and *not* post.el) to randomly pull a sig into each of my messages. If the random sig didn't really fit the occassion or person, I used to be able to issue a keystroke (or two? sigh) and it would go out and insert a new random sig (i.e. it would call randsig3 again and replace the old sig with a new one from my quote collection file). Can anyone enlighten this absent-minded professor? I promise I'll write it down this time. Thanks. dan -- Dan Resleremail: [EMAIL PROTECTED] Computer Science Dept. Virginia Commonwealth University Richmond, VA 23284-3068 USA
DSN
How can I set a delivery receipt? Are they reliable? I set: set dsn_notify='failure,delay,success' set dsn_return=hdrs But I get nothing back. It seems that my last experiment in this area( a few months ago) I got one receipt back in a great many trials. It is possible mutt is not compiled with dsn support. How do I know? Here is mutt -v: ystem: Linux 2.2.18 (i686) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. patch-1.5.tlr.mx_open_append.2 patch-1.3.28.rr.compressed.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list patch-1.3.27.bse.xtitles.1 patch-1.3.28.cd.purge_message.3 Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.28.cd.trash_folder.3.1 patch-1.3.28.cd.signatures_menu.2.1 patch-1.3.28.cd.pattern_broken.1 patch-1.3.28.cd.ifdef.1 patch-1.3.28.cd.edit_threads.9.2 patch-1.3.23.1.ametzler.pgp_good_sign -- Michael Montagne [[EMAIL PROTECTED]] 503.226.1575 --
Re: vi-style keybindings for mutt
* David Britton [EMAIL PROTECTED] [2002-08-15 17:35]: i hope you are aware that there is a lot to be changed to achieve vi modes there? Oh, I have a feeling it's more difficult than I want it to be, but I would like the change (I hit esc just about every time I go to edit a string in mutt). welcome to the club! ;-) Since I hardly ever use the arrow keys anywhere else, it'd be nice if mutt could be taken off the short list. eh? Sven
Re: Correcting bad From formats - alternates
* Andre Berger [EMAIL PROTECTED] [2002-08-15 14:44]: The following bad From formats are displayed with F flag in my index as if they were from me (andre): From: Luca Riazzi LRIAZZIremoveme-cancellami@writeme.com From: Neil Tisdale neil.discard[EMAIL PROTECTED] From: lst_cwby mailto:l_@m_@st_@n_@__c_@wb_@y@@bt_@nt_@[EMAIL PROTECTED]@m Can I work around this somehow? mutt uses $alternates to figure this out. what is the value you set? check with set ?alternates or with :set alttab=tab. Sven
Re: Running Mutt from a setgid program
* Al Weston [EMAIL PROTECTED] [2002-08-15 15:01]: We're having a problem running mutt from a program that is running setgid. Mutt produces the following error: mutt: I don't want to run with privileges! Everything is fine if we just run mutt from the command line, but we need to call it from within another program which is running setgid. Anyone know of a workaround for this one? don't run mutt within a privilidged environment? i wonder what forces you to do that. but i won't take guesses... DJB sig applies. Sven -- Note to experienced users: Please don't encourage anti-support behavior. Don't try to answer questions from users who don't provide the necessary information. Guessing what they did is an incredible waste of time. (DJB)
Re: DSN
* Michael Montagne [EMAIL PROTECTED] [2002-08-15 23:52]: How can I set a delivery receipt? I set [...] But I get nothing back. you'll get a receipt when the recipient's system supports it/ if not, well, then you don't. Are they reliable? no. the recipient can turn off DSN by request. It seems that my last experiment in this area (a few months ago) I got one receipt back in a great many trials. It is possible mutt is not compiled with dsn support. How do I know? you never know. but you can try.. Sven
Re: Correcting bad From formats - alternates
Sven Guckes wrote: * Andre Berger [EMAIL PROTECTED] [2002-08-15 14:44]: The following bad From formats are displayed with F flag in my index as if they were from me (andre): From: Luca Riazzi LRIAZZIremoveme-cancellami@writeme.com From: Neil Tisdale neil.discard[EMAIL PROTECTED] From: lst_cwby mailto:l_@m_@st_@n_@__c_@wb_@y@@bt_@nt_@[EMAIL PROTECTED]@m Can I work around this somehow? mutt uses $alternates to figure this out. what is the value you set? check with set ?alternates or with :set alttab=tab. That has nothing to do with what he was asking about. Those are obviously malformed addresses that Mutt shows as being sent by the user. This is really a bug in the way Mutt handles malformed addresses. If there is a parse error, Mutt will return NULL for the list of addresses. Normally this would not be a problem, but because some old mail clients that people used to use did not write a From: line in the mbox for saved outgoing messages, Mutt will assume that the message from you if there is no From: line. Since Mutt represents no addresses and bad addresses the same way internally, it can't tell the difference.
Re: auto_view with mutt in Cygwin?
* Sean LeBlanc [EMAIL PROTECTED] [2002-08-15 20:18]: I can't seem to figure out how to get mutt to dump html to lynx (or links) in Cygwin. I have the same setting I have on my FreeBSD box, but Mutt says: mailcap entry for type text/html not found for any html mail I get? ...and yet I have a text/html entry in my ~/.mailcap file. Anyone using mutt under Cygwin that has figured this out? did you check the files in $mailcap_path, too? Sven
Re: Correcting bad From formats - alternates
* Michael Elkins [EMAIL PROTECTED] [2002-08-16 00:41]: Sven Guckes wrote: * Andre Berger [EMAIL PROTECTED] [2002-08-15 14:44]: The following bad From formats are displayed with F flag in my index as if they were from me (andre): From: Luca Riazzi LRIAZZIremoveme-cancellami@writeme.com From: Neil Tisdale neil.discard[EMAIL PROTECTED] From: lst_cwby mailto:l_@m_@st_@n_@__c_@wb_@y@@bt_@nt_@[EMAIL PROTECTED]@m Can I work around this somehow? mutt uses $alternates to figure this out. what is the value you set? Those are obviously malformed addresses that Mutt shows as being sent by the user. This is really a bug in the way Mutt handles malformed addresses. If there is a parse error, Mutt will return NULL for the list of addresses. indeed - all addresses are invalid. i did not check them.. Normally this would not be a problem, but because some old mail clients that people used to use did not write a From: line in the mbox for saved outgoing messages, Mutt will assume that the message from you if there is no From: line. Since Mutt represents no addresses and bad addresses the same way internally, it can't tell the difference. well, there's a difference between No From: line and From: line contains no valid addresses, right? sound like a simple flag needs to be checked for the existance of a From: line.. is that all? To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Mail-Followup-To: [EMAIL PROTECTED], [EMAIL PROTECTED] changing over to mutt-dev? Sven
Re: sending with perl (was: The dreaded bare LF problem)
On 08-11 08:47, Cameron Simpson wrote: On 00:29 11 Aug 2002, Sven Guckes [EMAIL PROTECTED] wrote: | and why are you using a perl script | for sending when you have mutt? Because, as y'all keep saying, mutt doesn't send email or talk to SMTP servers. It hands messages to sendmail. I also use a perl script for this, and point mutt at it as the sendmail tool. It's especially handy on disconnected home machines which have net connections but not net-aware local mail systems; you can then just replace the sendmail with something that delivers, for example, to the host named by your $SMTPSERVER variable. I have other reasons too, but the above is a good one for some setups. This discussion rather quickly degenerated into the minutiae over how easy and what capabilities various MTAs have, but I can say the reason *I'm* using a script to send mail is because the ease of setting it up. If it works, why should I care whether someone else thinks it the best or not? I don't mean that to sound nasty, either. It's what works for me. One size does not fit all. In this case, smtp.pl had a nit in it, so I switched to ssmtp. Another reason is portability: I don't want to have to set up sendmail or the like under Cygwin just so I can use Mutt at work on Windoze. Sure sendmail, postfix, etc. are much more robust, can spool locally if remote server is down, etc...but I don't care. :) For me, open source is all about choice. I'm sure someone could demonstrably prove that Emacs, for example, is much more robust than vi...but Emacs isn't for everyone, either. I use Blackbox, even though KDE/GNOME have many more features...but again, it's all about choice, folks, and it's where open source has the upper hand on proprietary stuff, hands down. We should play on that strength. -- Sean LeBlanc:[EMAIL PROTECTED] The cruelest lies are often told in silence. -Robert Louis Stevenson
