Re: Question about upgrading from mutt-0.79
On Tue, Mar 02, 1999 at 10:24:38PM +0100, Dirk Foersterling <[EMAIL PROTECTED]> wrote: > On Thursday 18.02.1999 Dirk Foersterling ([EMAIL PROTECTED]) wrote: > > > > Hi! > > > > I'm trying to upgrade from mutt-0.79 to mutt-0.95. The Changelog doesn't > > seem to reach that far back... > > > > I got used to mutt's behaviour of saving read messages from mailing > > lists. If I received a mail from a list, then the save-message function > > (in conjunction with save_name set) saved it to a file named after the > > list name. For example, every mail that was sent "To: mutt-users@.." got > > stored in =mutt-users. > > > > With mutt-0.95.3, this seems to be impossible. Is it? > > > Sorry to anger you. Thanks for ignoring me. You failed on a question > that turned out to have a simple answer. However, it took me two weeks > to find out how the actions taken by the mutt-0.79 "lists" command can > be simulated with mutt-0.95. A simple pointer to what passage of the > manuals I should review would have been enough. Too late. Or did really > nobody know the answer? > > -dirk > > P.S.: Somwhow I was removed from the mailing list without further > notice. Do you dislike question-asking novices and upgraders that hard? Take a deep breath. Nobody here is out to get you. I saw your question, didn't know the answer off-hand, meant to look it up later, and forgot. Remember, answering mutt questions isn't anybody's job here, so sometimes something slips through the cracks. The best way to deal with this is to ask again, nicely. I'm glad you figured out the answer, if you even wanted to post it here, for others who may not know (I still haven't had a chance to figure out again, for instance) that would be helpful, too. You probably got unsubscribed from the list because your mail was bouncing at some point. It happens. I'm not sure that you are successfully resubscribed, because I had to approve your question by hand (I'm one of the list moderators at the moment) but maybe you just posted from a different address than you are now subscribed from? If you are unsubscribed, please feel free to resubscribe again (by sending mail to [EMAIL PROTECTED]). -Daniel -- Daniel Eisenbud [EMAIL PROTECTED]
'Catchup'
Is there any way to mark all posts in a mailbox read, without entering the box? m.
Re: Question about upgrading from mutt-0.79
On Tuesday 02.03.1999 Daniel Eisenbud ([EMAIL PROTECTED]) wrote: > > > > P.S.: Somwhow I was removed from the mailing list without further > > notice. Do you dislike question-asking novices and upgraders that hard? > > Take a deep breath. Nobody here is out to get you. *gasp* Okay. Thank you very much for replying after this one. I'll try to be a little more patient in future. > I saw your question, didn't know the answer off-hand, meant to look it > up later, and forgot. Remember, answering mutt questions isn't > anybody's job here, so sometimes something slips through the cracks. This seems to be an upgrade issue, too. Some time ago, every question produced LOTS of answers on mutt-users. > The best way to deal with this is to ask again, nicely. I'm glad you > figured out the answer, if you even wanted to post it here, for others > who may not know (I still haven't had a chance to figure out again, for > instance) that would be helpful, too. You will see it here. > You probably got unsubscribed from the list because your mail was > bouncing at some point. It happens. I'm not sure that you are I'm not aware of some bouncing or the like and I didn't receive any error message. So, I don't know how to prevent this yet. Regards, -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - "Da trennt sich dann die Spreuzen vom Wei!" - D. W.
mutt and dtmail anad attachments
Hello I have a problem (not really me, but my colleagues) with reading attachments in dtmail when mail was send in mutt. All email attachment are present as noname attachment in dtmail. Do you have a opinion why? -- Keso
=?ibm850?b?MC45NS4zOiBIb3cgdG8gdXNlIOT2/N/E1tzf4uru9Pvg6Ozy+eHp7fP6wsrO?==?ibm850?b?1NvAyMzS2cHJzdPa?=
Hi, You already know me ;-} I'm upgrading from 0.79... I have problems with the following characters (and probably more that I didn't try): äöüßÄÖÜâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ (Two lines if you can't display them:) """z"""^`'^`' aousAOUaeiouaeiouaeiouAEIOUAEIOUAEIOU Instead of these characters, the mutt pager only displays question marks. Similar with mutt's message menu: If a subject contains any of these characters (=??= translated), they are replaced by "." Not only displaying these characters fails. I cannot write any Subject: containing them. Mutt then only beeps instead of inserting the correct character. If I use mutt-0.79 instead, (compiled directly after 0.95.3 with the same compiler and libraries on the same system) reusing the same xterm window, everything works fine. So it must be a mutt configuration error (or a bug? Then I should have written to mutt-dev). Setting the charset variable didn't have any effect. I also tried S-Lang (9938) instead of ncurses and compiling mutt with and without NLS support. Nothing did help. Here are my mutt -v outputs. Mutt 0.79, Copyright (C) 1996,1997 Michael R. Elkins <[EMAIL PROTECTED]> 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 info: Linux 2.0.36 [using ncurses 3.0] Compile time definitions: -DOMAIN +USE_DOMAIN -HIDDEN_HOST -DONT_ADD_FROM -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_DSN -USE_8BITMIME -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR SENDMAIL="/usr/bin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/lib" -ISPELL _PGPPATH="/usr/bin/pgp" Mutt 0.95.3i (1999-02-12) Copyright (C) 1996-8 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: Linux 2.0.36 [using ncurses 3.0] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/bin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL _PGPPATH="/usr/bin/pgp" _PGPV2PATH="/usr/bin/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. As you can see, I had to use my old mutt-0.79 to write this message (Because of the subject line). -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - "Die 4-Stündige Klausur geht von 8:00Uhr bis 14:00Uhr" - R.K.
Re: 0.95.3: How to use õ÷³ThÍLTÔÛ¯¶¹ÓÞý=¨ßÚݾ·dUVÈFuUVÊuuDHËd
On Wed, 03 Mar 1999, Dirk Foersterling wrote: > Content-Type: text/plain; charset=ibm850 > I have problems with the following characters (and probably more that I > didn't try): > > õ÷³ThÍLÔÛ¯¶¹ÓÞý=¨ßÚݾ·dUVÈFuUVÊuuDHËd > (Two lines if you can't display them:) > > """z"""^`'^`' > aousAOUaeiouaeiouaeiouAEIOUAEIOUAEIOU You may not have understood the differences between different charsets? The characters you mean above come from iso-8859-1 (Latin1) but then you write in the header of your mail that you use ibm850. The old mutt 0.79 simply displayed every character as is and so you were able to read this. Newer versions come with much better charset code which finds the ibm850 in the header and knows that my xterm uses iso-8859-1 and so it converts the ibm850 chars to iso-8859-1. This leeds to the rubbish, I quoted above. > Instead of these characters, the mutt pager only displays question > marks. Then you may have a problem with your locale settings. Try setting the envionment variable LC_CTYPE (or LC_ALL, LANG) to some value supporting iso-8859-1 (e.g. "de_DE"). Ciao Roland -- * [EMAIL PROTECTED] * http://www.rhein.de/~roland/ * PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Re: 0.95.3: How to use äöüßÄÖÜßâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ
On Wed, Mar 03, 1999 at 10:57:01AM +0100, Dirk Foersterling wrote: > You already know me ;-} I'm upgrading from 0.79... > > I have problems with the following characters (and probably more that I > didn't try): > > äöüßÄÖÜâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ > > (Two lines if you can't display them:) > > """z"""^`'^`' > aousAOUaeiouaeiouaeiouAEIOUAEIOUAEIOU It looks like it worked for me - mutt 0.95i, using rxvt v2.20 See below for mutt -v -- Later ... Rich Roth --- On-the-Net Direct: Box 927, Northampton, MA 01061, Voice: 413-586-9668 Email: [EMAIL PROTECTED] Url: http://www.on-the-net.com ~~~ www.i-depth.com lets you Add Instant Depth to your Website~~~ ~~~ Adding depths to Web presences and Internet providers ~ Mutt 0.95i (1998-12-12) Copyright (C) 1996-8 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: Linux 2.0.29 [using slang 10202] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR +HAVE_PGP2 -BUFFY_SIZE -EXACT_ADDRESS -ENABLE_NLS +ENABLE_SLANG SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/bin/ispell" _PGPPATH="/usr/local/bin/pgp" _PGPV2PATH="/usr/local/bin/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. Feature patch: slang-lang 0.95-0.0.3 by Richard Roth
Re: Question about upgrading from mutt-0.79
Warning Could not process message with given Content-Type: multipart/signed; boundary=VS++wcV0S1rZb1Fb; micalg=pgp-md5;protocol="application/pgp-signature"
Re: Question about upgrading from mutt-0.79
On Tue, Mar 02, 1999 at 09:03:27PM -0800, Daniel Eisenbud wrote: > On Tue, Mar 02, 1999 at 10:24:38PM +0100, Dirk Foersterling ><[EMAIL PROTECTED]> wrote: > > On Thursday 18.02.1999 Dirk Foersterling ([EMAIL PROTECTED]) wrote: > > > I got used to mutt's behaviour of saving read messages from mailing > > > lists. If I received a mail from a list, then the save-message function > > > (in conjunction with save_name set) saved it to a file named after the > > > list name. For example, every mail that was sent "To: mutt-users@.." got > > > stored in =mutt-users. > > > > > > With mutt-0.95.3, this seems to be impossible. Is it? > > > > Sorry to anger you. Thanks for ignoring me. [] > > [] Too late. Or did really nobody know the answer? > > P.S.: Somwhow I was removed from the mailing list without further > > notice. Do you dislike question-asking novices and upgraders that hard? I saw the question, too, and I remember quickly glancing at what looked like the answer the folks on this list and I eventually worked out when I asked a slightly different version of that same question (i.e., using a subdirectory under ~/Mail to save each list's e-mail, e.g., mutt-users mail is saved to =mutt/mutt-users by default). At that point, I thought ``ok, it's already been answered...move on.'' > I saw your question, didn't know the answer off-hand, meant to look it > up later, and forgot. My guess is it's one (or both?) of two things: 1) I was wrong, and the response wasn't an answer after all, or 2) you got unsubscribed before the answer was sent, and never got it. Later, --jim -- 73 DE N5IAL (/4) | "Debating unix flavors in the context of anything [EMAIL PROTECTED] | Microsoft is like talking about which ice cream [EMAIL PROTECTED] | flavor tastes least like sawdust with turpentine Ft. Walton Beach, FL | sauce." --(void) in alt.sysadmin.recovery
record folder shortcut?
Until recently, mutt would recognize '<' as a short cut for the record folder. It seems it no longer recognizes it on the command line (0.95 and 0.96). It still recognizes '>' as a shortcut for the mbox folder. Within mutt, both are recognized: 'c<' opens the record folder, and 'c>' opens the mbox folder. In summary (under ksh): mutt -f \< # mutt quits with No such file or directory (errno = 2) mutt -f \> * mutt open with the mbox folder. Is this a mutt problem, or a problem with my setup? -- David Ellement
Re: record folder shortcut?
Le Wed 03/03/1999, David Ellement disait > > Is this a mutt problem, or a problem with my setup? Since it works perfectly on my 0.95.3, it must be a problem with your setup. -- Erwan DAVID| Domaine de Voluceau Trusted Logic | BP 105, 78153 Le Chesnay CEDEX France Je ne parle qu'en mon nom propre, et encore pas toujours.
Re: 0.95.3: How to use äöüßÄÖÜßâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ
At 8:09 AM EST on March 3 rfi from Rich Roth sent off: > On Wed, Mar 03, 1999 at 10:57:01AM +0100, Dirk Foersterling wrote: > > > You already know me ;-} I'm upgrading from 0.79... > > > > I have problems with the following characters (and probably more that I > > didn't try): > > > > äöüßÄÖÜâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ > > > > (Two lines if you can't display them:) > > > > """z"""^`'^`' > > aousAOUaeiouaeiouaeiouAEIOUAEIOUAEIOU > > It looks like it worked for me - mutt 0.95i, using rxvt v2.20 Bizarre...when I read Dirk's message they were garbled, but when Rich "quoted" them and sent them on using mutt 0.95i, they appeared as Dirk intended. The difference seems to be that Dirk's message was in Content-Type: text/plain; charset=ibm850 while Rich posted with the better known Content-Type: text/plain; charset=iso-8859-1 Apparently for some reason* Dirk's mutt 0.95i has a problem with ibm850 while Rick's doesn't and neither does Dirk's mutt 0.79. * Sorry I can't be more help than that. -- Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. -- Dick Brandon Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/ PGP Key: http://astro.utoronto.ca/~reid/pgp.html
Re: 0.95.3: How to use õ÷³ThÍLTÔÛ¯¶¹ÓÞý=¨ßÚݾ·dUVÈFuUVÊuuDHËd
On Wednesday 03.03.1999 Roland Rosenfeld ([EMAIL PROTECTED]) wrote: > > On Wed, 03 Mar 1999, Dirk Foersterling wrote: > > > Content-Type: text/plain; charset=ibm850 > > > I have problems with the following characters (and probably more that I > > didn't try): > > > > äöüThÖLâêîôûàèì=ùáéíóúdUVÔFuUVÒuuDHÓd > > > (Two lines if you can't display them:) > > > > """z"""^`'^`' > > aousAOUaeiouaeiouaeiouAEIOUAEIOUAEIOU > > You may not have understood the differences between different > charsets? The characters you mean above come from iso-8859-1 (Latin1) > but then you write in the header of your mail that you use ibm850. The Sorry. This is an artifact of my experiments with the charset variable. I wrote the message originally with mutt-0.95.3 (with the wrong setting), postponed it and continued with mutt-0.79 to be able to type the characters into the subject line. > iso-8859-1 and so it converts the ibm850 chars to iso-8859-1. This > leeds to the rubbish, I quoted above. I'm aware of what the charset types are. I simply forgot to reject from my last experiments. iso-8859-1 was the first charset I tried out. > Then you may have a problem with your locale settings. Try setting > the envionment variable LC_CTYPE (or LC_ALL, LANG) to some value > supporting iso-8859-1 (e.g. "de_DE"). I tried this now, but this doesn't help anything. However, just using mutt-0.79 in place of 0.95.3 displays everything fine. If I set pager=less, the charset displays fine also. The problem is just within mutt. What else could I have done wrong? -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - "Diese Rekursionen sind nicht mit den Haaren herbeigezaubert" - R.K.
Re: 0.95.3: How to use äöüßÄÖÜßâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ
On Wednesday 03.03.1999 Rob Reid ([EMAIL PROTECTED]) wrote: > Bizarre...when I read Dirk's message they were garbled, but when Rich > "quoted" them and sent them on using mutt 0.95i, they appeared as Dirk > intended. The difference seems to be that Dirk's message was in Sorry again. I made the mistake to not recover from my experiments with different charset settings. This has nothing to do whith my problem. If you insist, I may resend the message with the correct iso-8859-1 charset configured. However, this won't cure the problems I encountered. I swear. -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - A professor is one who talks in someone else's sleep.
Re: 0.95.3: How to use äöüßÄÖÜßâêîôûàèìòùáéíóúÂÊÎÔÛÀÈÌÒÙÁÉÍÓÚ
On 1999-03-03 11:08:55 -0500, Rob Reid wrote: > Apparently for some reason* Dirk's mutt 0.95i has a problem with > ibm850 while Rick's doesn't and neither does Dirk's mutt 0.79. Well, I guess that Dirk doesn't have the character set definition files installed. Newer mutts will do some automagic recoding when working on messages with different character sets. tlr -- http://home.pages.de/~roessler/
MH mail folders
Hi!
I have recently begun looking into mutt, and would like a little help. I
have been through the documentation, and looked all over the web pages but
can't really find any information on MH mail folders.
I read my mail during the day with exmh. I like this and don't want to
change. I use procmail to sort my mail into folders, which exmh picks up and
uses. When I am home, I have to use ssh over a slow link to get into my box,
and hence exmh is not feasible. Is there a way with mutt to use the folders I
have already existing and read my mail?
Any help is surely appreciated. If there is a document I should be looking
at, a nice point in the correct direction please :-)
Dale
--
/^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^V^^\
Dale Lovelace Coordinator : Red Hat Beta Team [EMAIL PROTECTED]
ultimate_answer_t deep_thought(void) {
sleep(years2secs(750));
return 42;
}
quoting and long lines
I've looked through the archives and haven't found anything quite like what I'm looking for, hopefully someone will have some ideas... I'm around a lot of users who don't wrap at 72 or 76 columns, and so everytime I reply to their message, I get the first line with the quote-char in front of it, and the rest "unquoted". I've thought about using an external program like fmt to fmt the text before passing it into my editor (vim) but I also want to append a ">" before each new line to make it nicely quoted. I also tried setting the editor to fmt | vim but that doesn't work either :) Do I need to filter somehow? I'm probably missing some RTFM here, but does anyone have a nice macro that will do something like this? Will Newsbody do it? Thanks... -J
Re: 0.95.3: How to use õ÷³ThÍLTÔÛ¯¶¹ÓÞý=¨ßÚݾ·dUVÈFuUVÊuuDHËd
On Wed, 03 Mar 1999, Dirk Foersterling wrote: > > Then you may have a problem with your locale settings. Try setting > > the envionment variable LC_CTYPE (or LC_ALL, LANG) to some value > > supporting iso-8859-1 (e.g. "de_DE"). > I tried this now, but this doesn't help anything. What exactly did you try? Please try to run the program locale and have at the LC_CTYPE line. This line should point to a iso-8859-1 aware setting, I prefer de_DE. This presumes that you have proper locale files installed in /usr/[share|lib]/locale (depending on your libc version). If all this all doesn't work you may run ./configure with the option --enable-locales-fix, this will tell mutt that iso-8859-1 is always printable. Please note that this isn't a solution for your problem but only a workaround for your broken locales. If you want so solve the problem, correct the locale files (every good distribution should offer the locale files in combination with the libc). Ciao Roland -- * [EMAIL PROTECTED] * http://www.rhein.de/~roland/ * PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Re: quoting and long lines
I'm sure there are other ways to handle this, but I use Par[1], somewhat
integrated with my editor of choice Jove, to deal with it. I've got Par
installed. The Par package provides a utility named "par", which can be run
like "fmt" to filter a chunk of text and re-wrap it. It has a couple of big
advantages over fmt: it uses a sophisticated algorithm (the same sort of
algorithm as TeX) for filling text; so it attempts to find the best line
breaks using a "global" analysis of a whole paragraph, rather than just
blindly forcing as many words onto each line as will fit.
And (more to the point for this discussion) it attempts to automatically
detect prefixes, and handle them intelligently. It gets it right often enough
so I routinely expect to be able to use it to re-wrap a paragraph that is
quoted with the email-standard prefix of one or more ">" and a space, and
preserve the quoting properly.
When I said "somewhat integrated with ... Jove", here's what I use; in my
$HOME/.joverc, I have the lines:
define-macro par-fill-paragraph
^F^[xbackward-paragraph^M^@^[]^[xfilter-region^Mpar w78^M^F
bind-macro-to-key par-fill-paragraph ^[j
This makes M-j (default bound to the builtin "fill-paragraph", which
implements essentially the identical algorithm to fmt(1)) pipe the current
paragraph through "par w78".
Like I said, I'm sure there are other ways to handle this, and it could well
be that some of 'em are better. I've used this solution for years, with many
MUAs and newsreaders.
Warning: the Par documentation is bad. It is _so_bad_ ("How bad is it", I hear
you cry) it is _So_Bad_, that it comes with an apology. Don't try to
understand it, it will make your head explode. Just shove text through par(1),
and if you want a different margin use an argument of "wNN" to specify the
margin width.
-Bennett
[1] http://www.cs.berkeley.edu/~amc/Par/>
Re: 'Catchup'
On Tue, Mar 02, 1999 at 11:25:50PM -0600, Martin Julian DeMello wrote: > Is there any way to mark all posts in a mailbox read, without entering the > box? Without entering the box? Here's how to do it without even running mutt :) Mark everything old: cat the_mailbox_name | formail -s formail -I 'Status: O' >> the_new_mailbox Mark everything read: cat the_mailbox_name | formail -s formail -I 'Status: R' >> the_new_mailbox Mark everything new: cat the_mailbox_name | formail -s formail -I 'Status' >> the_new_mailbox You could probably do some macro magic to do this within mutt. David -- David Shaw | [EMAIL PROTECTED] | WWW http://www.jabberwocky.com/ +---+ "There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." - Jeremy S. Anderson
Re: quoting and long lines
This is what I do. (almost stock vi) Go to first line to be "fixed". ma Go to last line to be "fixed" - note that there should be no formatted (indented, etc.) text in between. mb (not really necessary, but the next step may move the focus line) :'a,'bs/^> // (gets rid of quoting) :'a,'b! fmt You may now have a new end of line, but 'a should still exist. Go to the end again: :'a,.s/^/> / Ideally, mutt would be able to do this for me, but _I'M_ not writing it - these types of text manglings are messy and can verge on religion. On Wed, Mar 03, 1999 at 10:27:37AM -0800, Jeff wrote: > I'm around a lot of users who don't wrap at 72 or 76 columns, and so > everytime I reply to their message, I get the first line with the > quote-char in front of it, and the rest "unquoted". I've thought about > using an external program like fmt to fmt the text before passing it into > my editor (vim) but I also want to append a ">" before each new line to > make it nicely quoted. I also tried setting the editor to fmt | vim but > that doesn't work either :) > > Do I need to filter somehow? > > I'm probably missing some RTFM here, but does anyone have a nice macro > that will do something like this? Will Newsbody do it? > > Thanks... > > -J > -- Jeffrey Haas [EMAIL PROTECTED] "Place all beliefs in proper receptacle"
Re: quoting and long lines
On Wed, Mar 03, 1999 at 10:27:37AM -0800, Jeff wrote: > I'm around a lot of users who don't wrap at 72 or 76 columns, and so > everytime I reply to their message, I get the first line with the > quote-char in front of it, and the rest "unquoted". I've thought about > using an external program like fmt to fmt the text before passing it into > my editor (vim) but I also want to append a ">" before each new line to > make it nicely quoted. I also tried setting the editor to fmt | vim but > that doesn't work either :) vim is able to do this. the 'gq' Command reformats text, and keeps the quoting. so 'gq ' should reformat your long line. CU, Sec -- Treat your password like your toothbrush. Don't let anybody else use it, and get a new one every six months. --Clifford Stoll
Re: 0.95.3: How to use õ÷³ThÍLTÔÛ¯¶¹ÓÞý=¨ßÚݾ·dUVÈFuUVÊuuDHËd
Dirk Foersterling <[EMAIL PROTECTED]> wrote: > > > Then you may have a problem with your locale settings. Try setting > > the envionment variable LC_CTYPE (or LC_ALL, LANG) to some value > > supporting iso-8859-1 (e.g. "de_DE"). > > I tried this now, but this doesn't help anything. Well, every OS implements locales differently. We can't give you a specific formula for setting your $LANG environment variable, because we don't know what locales are available on your OS. You will have to give us more info (such as the "mutt -v" output). As an example, I use HP-UX 10.20. When I run the command "locale -a", I get a list of all the supported locales. In scanning the list, I found this setting: en_US.iso88591 If I set $LANG to this value, Mutt is then able to display ISO-8859-1 characters correctly, because I have told it that this is my chosen locale, and it can determine that these characters are printable. > However, just using mutt-0.79 in place of 0.95.3 displays everything > fine. If I set pager=less, the charset displays fine also. The > problem is just within mutt. This is not really a "Mutt is doing something wrong" problem. This is a "Mutt is trying to be smarter than it used to be, and is failing because you haven't given it enough information" type of problem. Technically, your version of "less" is broken, or rather, not very smart, because it is assuming that those ISO-8859-1 characters are printable, when there is no such guarantee. Without a proper $LANG setting, it *should* assume that they are not printable, the same way that Mutt-0.95 does. So, the answer is to find out, for your OS, what is the proper setting for $LANG? Then set this value, and run Mutt again, to see it take effect. We've all had to do this. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Bleh - MS attachements
Is there any patch, utility, script or something which can decode typical MS-attachements like [applica/ms-tnef, base64, 1.4M] As I continually get these type of attachements life is really annoying, as I can't decode them (and the senders won't attach in another format). -- Christian Stigen Larsen -- http://www.sublevel3.org [EMAIL PROTECTED]http://www.stud.ntnu.no/~chrisl/
Re: Question about upgrading from mutt-0.79
Dirk Foersterling <[EMAIL PROTECTED]> wrote: > > > You probably got unsubscribed from the list because your mail was > > bouncing at some point. It happens. I'm not sure that you are > > I'm not aware of some bouncing or the like and I didn't receive any > error message. So, I don't know how to prevent this yet. My previous ISP was rather unreliable with mail. My mail would sometimes bounce for random transient failures, and of course the system wouldn't notify *me* that it bounced one of my messages. If it knew how to get mail to me, it would've simply sent the mail through to me without bouncing, right? So the only way I could ever find out about it was when friends would tell me that my mail was bouncing. It simply appeared to me that I wasn't receiving any mail at the moment. So, while I can empathize with your situation, I can't offer any solution, other than to bother your ISP and ask them to look into the mail logs and found out why mail to you bounced during those certain days. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: MH mail folders
Dale Lovelace <[EMAIL PROTECTED]> wrote: > > I have been through the documentation, and looked all over the web > pages but can't really find any information on MH mail folders. That's because there is nothing particular special about MH folders. If you simply tell Mutt the location of the folder, it will detect that it is an MH folder, and read it. Do you find that this doesn't work? Use the standard settings: set folder = ~/Mail # Or wherever procmail's $MAILDIR is set set spoolfile = +INBOX # If your inbox is not in the default location mailboxes ! +mailbox1 +mailbox2 +mailbox3 # Boxes you like to read It should "just work." :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: 'Catchup'
1999-03-03-19:15:13 David Shaw: > 1999-03-03-05:25:50 Martin Julian DeMello: > > Is there any way to mark all posts in a mailbox read, without entering the > > box? > > Without entering the box? Here's how to do it without even running mutt :) I thought about posting essentially that, only for Maildir format; I use the simplest mv the_mailbox_name/new/* the_mailbox_name/cur although strictly speaking that's not quite right; I should do something like (cd the_mailbox_name/new;ls|perl -lne 'rename $_,"../cur/$_:2,S"') or thereabouts to add the "flags" to the filename. Mutt doesn't seem to mind my Maildir abuse, though:-). -Bennett
Re: Question about upgrading from mutt-0.79
Dirk Foersterling <[EMAIL PROTECTED]> wrote: > > Thanks for ignoring me. You failed on a question that turned out to > have a simple answer. For some reason, you never posted the answer, which future mutters might appreciate. save-hook ~l +%B -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: quoting and long lines
Jeff <[EMAIL PROTECTED]> wrote: > I'm around a lot of users who don't wrap at 72 or 76 columns, and so > everytime I reply to their message, I get the first line with the > quote-char in front of it, and the rest "unquoted". I've thought about > using an external program like fmt to fmt the text before passing it into > my editor (vim) but I also want to append a ">" before each new line to > make it nicely quoted. I also tried setting the editor to fmt | vim but > that doesn't work either :) Hm, your idea is good, but you missed something. You reply the message as normal and then pipe the text in vim through fmt -p'>' or par -p5 or any number. Ciao Christian -- /* http://www.rhein-neckar.de/~jupiter/Christian Kurz */
Re: Question about upgrading from mutt-0.79
On Tuesday 02.03.1999 rex ([EMAIL PROTECTED]) wrote: > > Hello Dirk, > > I have the same question (how to save list mail with the list > address). There have to be save-hooks created. Example for mutt users. lists mutt-users save-hook '~C mutt-users' =mutt-users The ~C means that messages sent to or carbon copied to mutt-users should go into =mutt-users. To reply to a list, you may type "L" instead of "r" (with the standard key bindings). -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - FATAL! Error writing signa314' mäö#ü433 vkvcv,.a4o 4'3 ß
quoting and long lines
I've looked through the archives and haven't found anything quite like what I'm looking for, hopefully someone will have some ideas... I'm around a lot of users who don't wrap at 72 or 76 columns, and so everytime I reply to their message, I get the first line with the quote-char in front of it, and the rest "unquoted". I've thought about using an external program like fmt to fmt the text before passing it into my editor (vim) but I also want to append a ">" before each new line to make it nicely quoted. I'm probably missing some RTFM here, but does anyone have a nice macro that will do something like this? Will Newsbody do it? Thanks... -J
Re: Bleh - MS attachements
Christian Stigen Larsen <[EMAIL PROTECTED]> wrote: > > Is there any patch, utility, script or something which > can decode typical MS-attachements like > > [applica/ms-tnef, base64, 1.4M] Try this URL: http://www.fiction.net/blong/programs/#tnef2txt -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Bleh - MS attachements
On Wed, Mar 03, 1999 at 08:12:54PM +0100, Christian Stigen Larsen wrote: > Is there any patch, utility, script or something which > can decode typical MS-attachements like > > [applica/ms-tnef, base64, 1.4M] I doubt there is one. I believe it should make hard use of OLE stuff or something alike. Anyway, it has nothing of use. To my mind, at least. :) Formattings, attachment placement, etc. Yes, sometime this very attachment may contain all the stuff, but this is rather rare. You may try to ask your [usual] correspondents to turn so called `Rich-text' option off when sending e-mail to you. -- Mike
Re: Question about upgrading from mutt-0.79
Warning Could not process message with given Content-Type: multipart/signed; boundary=5V5c01chtBAiSHoy; micalg=pgp-md5;protocol="application/pgp-signature"
Re: Question about upgrading from mutt-0.79
On Wed, Mar 03, 1999 at 09:57:23AM +0100, Dirk Foersterling <[EMAIL PROTECTED]> wrote: > On Tuesday 02.03.1999 rex ([EMAIL PROTECTED]) wrote: > > > > Hello Dirk, > > > > I have the same question (how to save list mail with the list > > address). > > There have to be save-hooks created. Example for mutt users. > > lists mutt-users > save-hook '~C mutt-users' =mutt-users > > The ~C means that messages sent to or carbon copied to mutt-users should > go into =mutt-users. This is not the optimal answer, though (I could have told you this much off the top of my head in the first place, but I knew there was a better way, I just forgot what it was.) See David DeSimone's post for an answer that doesn't require a save-hook for every list. -Daniel -- Daniel Eisenbud [EMAIL PROTECTED]
Re: timing vs diff (was Re: macro vs. typing keys in)
On Wed, Mar 03, 1999 at 13:45:41 -0500, David Thorburn-Gundlach wrote:
> ...and then Byrial Jensen said...
> % Please try the attached patch to 0.95.1. It sets the time stamp of
> % a new file to `one second ago'.
>
> I have applied this patch to my 0.95.3i sources and it all seems to be
> there, and my abort_unmodified var is set to "yes", but I still have
> to select "q" and say "n" to postponement. Is there something I
> should set differently, or does the patch not really work as
> advertised with 0.95.3i?
Sorry! It doesn't work as advertised with any version because of a
little bug. Please try the patch attached here instead.
Regards,
- Byrial
--- send.c.bak Wed Mar 3 22:11:30 1999
+++ send.c Wed Mar 3 22:18:10 1999
@@ -33,6 +33,9 @@
#include
#include
#include
+#include
+#include
+#include
#ifdef _PGPPATH
#include "pgp.h"
@@ -1072,9 +1075,20 @@ ci_send_message (int flags, /* send mod
{
struct stat st;
time_t mtime;
+struct utimbuf utim;
stat (msg->content->filename, &st);
mtime = st.st_mtime;
+if (mtime == time (NULL))
+{
+ /* Decrease the file's modification time by 1 second so we are sure
+ * to find out if the `editor' program changes it in less than 1 second.
+ */
+ mtime -= 1;
+ utim.actime = mtime;
+ utim.modtime = mtime;
+ utime (msg->content->filename, &utim);
+}
mutt_update_encoding (msg->content);
[Announce] Mutt 0.95.4 is out.
Mutt 0.95.4 is out. This version should be considered BETA. The distribution tar-balls and PGP checksums can be found under the following URL: ftp://ftp.guug.de/pub/mutt/ The following mirror sites should carry the new release quite soon: ftp://ftp.gbnet.net/pub/mutt-international/ ftp://ftp.fu-berlin.de/pub/unix/mail/mutt/ ftp://pgp.rasip.fer.hr/pub/mutt/international/ ftp://ftp.gwdg.de/pub/unix/mail/mutt/ ftp://ftp.iks-jena.de/pub/mitarb/lutz/crypt/software/pgp/mutt/ ftp://ftp.lip6.fr/pub/unix/mail/mutt/ ftp://ftp.arch.pwr.wroc.pl/pub/mutt/ ftp://ftp.uib.no/pub/mutt/ ftp://gd.tuwien.ac.at/infosys/mail/mutt-intl/ ftp://ftp.spyda.net/pub/mutt/ As usual, the "i" version is the one with the PGP support. Major changes since 0.95.3 - Mutt up to version 0.95.3 was affected by a temporary file related race condition which could lead to security-relevant problems. - We have fixed a bug which would lead to crazy behaviour when a message was listed in it's own References header. - IMAP and MIME should mix better now. Major changes since 0.95 - Mutt was affected by the so-called "pine remote exploit". We have implemented a work-around we believe to be safe. See README.SECURITY and the mailcap_sanitize option for details, and check your mailcap files for insecure entries. - The use_mailcap option has gone. Instead, we now have implicit_autoview. See the manual for details. - Mutt now uses version 0.12 of the "regex" library instead of rx. This library is believed to be far more stable than rx. See INSTALL for details. -- http://home.pages.de/~roessler/
