Re: [Announce] mutt-1.1.8 is out
On Sat, Mar 04, 2000 at 02:19:36PM +0100, Thomas Roessler wrote: :Mutt-1.1.8 is out. This is another BETA version. Changes :against 1.1.7 include fixes for one recent and one :long-standing, but mostly unnoticed bug. Just a quick observation. Mutt is one of the few pieces of software that gets full version numbers for betas, versus most conventions that use a next-version-number + "b" + beta-version-number. I just found this practice to be a bit unusual. :) -- Eugene Lee [EMAIL PROTECTED]
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
Bennett Todd <[EMAIL PROTECTED]> writes:
>Note to the procmail-list folks, the mutt list grew this thread that
>spawned the question, how to deliver to Maildirs safely from an old,
>musty, non-maildir-supporting procmail. Various suggestions were
>bashed back and forth, and after I read the thread it looked to me
>like we were closing in on something actually [potentially] useful.
>Supposing a user's ISP won't upgrade their procmail, or allow them
>to install a nice tight efficient compact maildir.c executable, how
>about something like:
>
> # Needed only once, in the preamble of the procmailrc
> XXX=`date +%S`.$$.$HOST
That isn't particularly unique: %S is just the seconds of the minute.
Perhaps you meant %s, GNU's extension that gives the time_t value
(number of seconds since midnight 1970-1-1). That would be almost
certainly unique: pids are *very* unlikely to be resused within a second.
> # other recipes may come here
>
> :0
> * ^Sender: [EMAIL PROTECTED]
> {
> :0 fw
> |cat >mutt/tmp/$XXX
>
> :0 a
> |mv mutt/tmp/$XXX mutt/new/$XXX
> }
At least, you should lose the 'f' flag on the first nested recipe and
instead put the 'i' flag on the second. That's more efficient and doesn't
create problems if the mv fails for some reasons. In the above, if the
mv fails then you lose the message. Dropping the 'f' flag and adding the
'i' preserves the message past failures.
However, since you're trusting for $XXX to be unique, you might as well
go all the way and save two processes (a shell and the cat) by saving
the message directly:
:0
* conditions
{
:0
foldername/tmp/$XXX
:0 ai
|mv foldername/tmp/$XXX foldername/new/$XXX
}
If the fact that procmail might just append to an existing file (what
is it doing there anyway?), then go back to the cat, but combine the
actions:
:0 w
* conditions
|cat >foldername/tmp/$XXX && \
mv foldername/tmp/$XXX foldername/new/$XXX
The middle recipe will be faster though...
Philip Guenther
Re: [Announce] mutt-1.1.8 is out
On Sun, Mar 05, 2000 at 03:53:48AM -0800, Eugene Lee wrote: > Just a quick observation. Mutt is one of the few pieces of software Few -- like the Linux Kernel? > that gets full version numbers for betas, versus most conventions that > use a next-version-number + "b" + beta-version-number. I just found > this practice to be a bit unusual. :) Even numbers -- releases odd numbers -- betas -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb "One smaller motivation which, in part, stems from altruism is Microsoft-bashing."- Vinod Valloppillil (Microsoft) PGP signature
Extra space in Subject
Hi, I have a small problem. I have noticed that mutt inserts a space in the subject field between the 'Re:' and the actual subject everytime i reply to someone. In other words: Subject: Re: Foobarbaz becomes Subject: Re: Foobarbaz Subject: Re: Foobarbaz Subject: Re: Foobarbaz everytime i reply. Any idea where this comes from, and what i should do to avoid this behaviour? -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers Destroy a spamhaus! http://www.xs4all.nl/~sister/mirror/sengir/spam_sites.html
Re: Extra space in Subject
On Sun, 05 Mar 2000, Rejo Zenger wrote:
> Subject: Re: Foobarbaz
> Subject: Re: Foobarbaz
> Subject: Re: Foobarbaz
>
> everytime i reply. Any idea where this comes from, and what i should
> do to avoid this behaviour?
Looks like you have a bad reply_regexp setting. If this only matches
"Re:", it will only remove "Re:" and not "Re: " and after removing
"Re:" and adding "Re: " after this, you will note the mentioned
effect. The default reply_regexp ("^(re|aw):[ \t]*") should not show
this behavior.
Tscho
Roland
--
* [EMAIL PROTECTED] * http://www.spinnaker.de/ *
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
Philip Guenther <[EMAIL PROTECTED]> wrote on Sat, 04 Mar 2000:
> However, since you're trusting for $XXX to be unique, you might as well
> go all the way and save two processes (a shell and the cat) by saving
> the message directly:
>
> :0
> * conditions
> {
> :0
> foldername/tmp/$XXX
>
> :0 ai
> |mv foldername/tmp/$XXX foldername/new/$XXX
> }
This has the problem that message files within maildirs are not supposed
to have the leading "From ", which this will create. Not a big problem
in practice probably, but a violation of the standard anyway. And you
likely can't get rid of the "From " with just procmail anyway, you'd
need some other tool for that (I haven't investigated this).
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Bumper sticker: Cover me. I'm changing lanes.
Re: mutt and mh/procmail
I'll add my thanks, too. The support available here has been most welcome. Phil On Sun, Mar 05, 2000 at 12:00:39AM -0600, Conrad Sabatier wrote: > Just wanted to say "Thank you very much" for all the great responses in > this thread. Not only is Mutt a great mail app, but its users are the > greatest, too! > > I've changed my MH boxes over to Maildir format, and I must say, Mutt is > certainly working much better now. And luckily, my version of procmail > supports the folder/ syntax, so changing my .procmailrc was a snap, too. > > The more I use and learn about this progrma, the more I like it! What trn > is to news, mutt is to mail. :-) > > Thanks again, everyone. > > -- > Conrad Sabatier > http://members.home.net/conrads/ > ICQ# 1147270 -- Phil Staub, KE7HC [EMAIL PROTECTED] "Unix: because reboots are for hardware upgrades!"
Re: Reading HTML Attachments
Pete, You're right! The Gnome terminal is a spendid answer! Part of me wants a non-mouse based solution, I think this is the answer for me. On Thu, Mar 02, 2000 at 10:20:51AM -0500, Pete Toscano wrote: > john, > > this could be done by running mutt in the right terminal. i'll bet an > analogue exists in kde, but in gnome, just run mutt in a gnome-terminal. > you'll notice that when you move the mouse over a url, such as in > kevin's sig below, the pointer will turn to a pointing hand and the url > will be underlined. if you right-click on that, a menu will pop-up and, > at the bottom of that menu, the option "open in browser" will appear. > i'm sure you can figure out the rest. =8] > > hth, > pete > > On Wed, 01 Mar 2000, John P. Verel wrote: > > > Kevin, > > > > Thanks. Worked like a charm! Now, next project is to be able to > > "click" on imbeded hyperlinks. The mutt manual (4.12) refers to an > > external urlview program. I'm unclear what the manual means in > > referring to macro indexetc. Have you done this? > > > > On Wed, Mar 01, 2000 at 06:58:08PM -0800, -kevin- wrote: > > > John, > > > > > > On 00-03-01 20:46, John P. Verel wrote: > > > > My mailcap entry looks like this: > > > > > > > > text/html; netscape -remote openURL\(%s\) > > > > > > Change to: > > > > > > text/html; netscape -remote 'openFile(%s)';copiousoutput > > > > > > -- > > > -* -kevin-*- > > > -* sick with the good infection *- > > > -* [EMAIL PROTECTED] *- > > > -* http://www.pobox.com/~kathey *- > > > > -- > Pete Toscano h:[EMAIL PROTECTED]w:[EMAIL PROTECTED] > GPG fingerprint: AE5C 18E4 D069 76D3 9B9C D226 D86A 522F 446C 767A
Re: emacsclient (But really status_format!)
At 12:54 AM EST on March 4 Raju K V sent off: > hi, > > In the screenshot of mutt in your page, some details of email are shown > in the staus bar. how do you do this? Oddly enough, the format for the status bar is described in the manual under "status _format". RTFM... set status_format="-%r %f [%?M?%M/?%?m?%m msgs, ?%?n?%n new, ?%?d?%d del, ?%?F?% F flag, ?%?t?%t tag, ?%?p?%p postponed, ?%?b?%b box(es), ?%l bytes] --(%s)%|-" > On Fri, Mar 03, 2000 at 12:54:48PM -0500, Rob Reid [[EMAIL PROTECTED]] wrote: > > At 6:08 AM EST on March 3 Ralf Hildebrandt sent off: > > > On Thu, Mar 02, 2000 at 06:36:15PM -0800, ashley wrote: > > > > I'm new to mutt. I read in the FAQ about emacsclient as an editor (rest of entire emacsclient thread snipped.) Some things that might not be in the fine manual are: 0. "Don't quote previous messages after your new text; it's ass backwards!" 1. "NEVER quote entire messages, only quote the relevant material, with your additions immediately underneath." 2. "Don't inject a completely different topic into a thread and expect anyone to find it and understand or care what you're talking about. Got a new topic? Start a new thread!"* 3. "Don't combine the above sins!" * Actually I understand the temptation, and will suggest a new feature in a different thread. -- D'oh! English! Who needs that? I'm never going to England. - Homer Simpson, talking Barney into cutting class in The Way We Was Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/ PGP Key: http://astro.utoronto.ca/~reid/pgp.html
