Re: speed of cacheing depends on terminal?

2008-05-10 Thread Christian Ebert
* [EMAIL PROTECTED] on Saturday, May 10, 2008 at 18:07:04 -0400
> 1.5.17 with header caching enabled.  I've got read_inc and
> write_inc set to 1000.  Nevertheless, I've noticed that the
> process of evaluating the cache (when I switch into a big
> folder) is significantly slower when I use Terminal.app than if
> I use xterm/rxvt over Apple's X11.

I never experienced that. Overall xterm might behave crisper,
because Terminal.app is slow -- but not only for mutt.

I do however notice slowness right after starting mutt (cold
cache???), but then it runs fine.

> FWIW: I built using the BerkeleyDB libraries, since the other
> choices refuse to work with OSX.  (Actually, I finally got mutt
> to build with gdb, but mutt behaved *really* weird with
> screen-drawing, so gdb is a no-go on OSX).

I always used and use qdbm w/o prob. Both qdbm and mutt build
just fine on 10.4.11. Also fink's mutt ships with qdbm. If with
"gdb" you mean GNU dbm I once built mutt against gdbm from fink,
again w/o without having the issues you describe.

c
-- 
Python Mutt utilities 


Re: pass single-quoted arguments to external script

2008-05-10 Thread David Champion
> So how do I properly escape the single quotes in the vim args

Personally, as soon as I start having trouble figuring out how to quote
things withing multiple layers of parser, I ditch the headache and
put the command into an external script that accepts only the minimum
arguments from mutt (i.e., the values that only mutt knows).

In you case, I guess that would be approximately:

send-hook ... 'set editor=mutt-xvim'

$ cat mutt-xvim
#!/bin/sh
exec xterm -e vim '+/^--[ ]*$' -c 'read ' "$@"

I know that's a level of abstraction away from what you were aiming for,
but time is just too precious to spend it on all the various (and they
indeed vary) quoting idiosyncrasies, unless that sort of thing is fun or
educational for you.  And by putting mutt-specific scripts into a mutt
namespace, as it were, you're not really causing any layering conflicts.

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago


Re: speed of cacheing depends on terminal?

2008-05-10 Thread Sahil Tandon
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [05-10-2008]:
  
> 1.5.17 with header caching enabled.  I've got read_inc and write_inc 
> set to 1000.  Nevertheless, I've noticed that the process of 
> evaluating the cache (when I switch into a big folder) is 
> significantly slower when I use Terminal.app than if I use xterm/rxvt 
> over Apple's X11.

I run Mutt 1.5.17 via Terminal.app (on Leopard) with no such speed 
issues.  I installed via macports.

-- 
Sahil Tandon <[EMAIL PROTECTED]>


speed of cacheing depends on terminal?

2008-05-10 Thread dv1445
Hello,

1.5.17 with header caching enabled.  I've got read_inc and write_inc set to 
1000.  Nevertheless, I've noticed that the process of evaluating the cache 
(when I switch into a big folder) is significantly slower when I use 
Terminal.app than if I use xterm/rxvt over Apple's X11.

This is puzzling, since I thought caching has nothing to do with the terminal 
choice.  Anybody know why this would be, and/or how I can do something about it?

FWIW: I built using the BerkeleyDB libraries, since the other choices refuse to 
work with OSX.  (Actually, I finally got mutt to build with gdb, but mutt 
behaved *really* weird with screen-drawing, so gdb is a no-go on OSX).

Thanks.
-gmn



too much header fetching

2008-05-10 Thread dv1445
Hello,

I have some mailing list archives kept in mailboxes over IMAP.  I have header 
caching enabled on 1.5.17.  Usually when I switch to those folders, mutt 
"evaluates" the caches, which is a process that's considerably faster than 
"fetching the headers" (indeed, that's the point of caching).  But sometimes 
lately, when I switch into one of these folders, mutt will begin fetching anew 
as if I had no cache built up.  Well, that's not quite true: mutt begins 
fetching anew as if I only had a small fraction of the cache that I actually 
do.  I've got ~15K mails in this folder.  Sometimes for no reason mutt will 
start fetching headers starting with a seemingly random #, like 4517 or 3387.  
This is really annoying, since fetching takes a *long* time with 15K mails.

Anybody got a clue?  I've never had this happen before until recently.
-gmn



Re: htmlview

2008-05-10 Thread Sahil Tandon
* hce <[EMAIL PROTECTED]> [2008-05-10 20:48:22 +1000]:

> Does that mean it is not the mutt feature, rather the FC specific? How
> can I make Debian work to display HTML emails the same way as FC6
> does?
  
You can configure mutt to display non-plaintext emails in a variety of 
ways.  Read the manual, specifically the section on MIME Support:

http://www.mutt.org/doc/manual/manual-5.html

> > Quite, much better without htmlview and doing it the 'user driven' 
way
> >  that gives you what you specify rather than what the distribution
> >  guesses you might want.
> 
> Would you please explain more what is the "user driver" way to achive 
that?

Read the manual linked above and set your mailcap as you wish.

-- 
Sahil Tandon <[EMAIL PROTECTED]>


pass single-quoted arguments to external script

2008-05-10 Thread Steve S
Hi all.

I have some trouble with Mutt's quoting conventions in hooks etc.

At first, what I already have and what works is (a) or (b), which does the
same:

a) send-hook ... "set editor=\"vim '+/^--[ ]*$' -c 'read ' \" "
b) send-hook ... 'set editor="vim '\''+/^--[ ]*$'\'' -c '\''read 
'\'' " '

Now, I want to replace `vim` with a script `xvim` which essentially does:

xterm -e vim "$@" &

Simply dropping `xvim` into (a) fails:

send-hook ... "set editor=\"xvim '+/^--[ ]*$' -c 'read ' \" "

I get a vim error:

"]*$" [New File]
Error detected while processing command line:
E486: Pattern not found: ^--[
E16: Invalid range: -2
Press ENTER or type command to continue

i.e. the single-quotes are eaten up and the cmd line args are split at
whitespaces. I tried to escape the single quotes. Increasing the number of `\'
changes nothing until I use four: ' which produces a mutt error:

Error running "xvim \'+/^--[ ]*$\' -c \'-2; read 
/home/elcorto/.mutt/greeting_mefx.txt\'  '/tmp/mutt-ramrod-1000-9263-0'"!

So how do I properly escape the single quotes in the vim args

 '+/^--[ ]*$'
 -c 'read '

TIA!

steve


Re: htmlview

2008-05-10 Thread hce
On 5/10/08, Chris G <[EMAIL PROTECTED]> wrote:
> On Sat, May 10, 2008 at 10:00:08AM +0200, Ionel Mugurel Ciobica wrote:
>  > On 10-05-2008, at 10h 26'28", hce wrote about "htmlview"
>  > > Hi,
>  > >
>  > > I've set mutt in two machines, one in FC6 and another in Debian. The
>  > > FC6 installed htmlview, the FC6 mutt automatically launchs a brower
>  > > for viewing html emails. In Debian, I could not find htmlview package
>  > > for that feature. What package should I install in Debian to get
>  > > automatically launch a brower to view HTML emails like it in FC6?
>  > >
>  >
>  > What is "FC6"? Did you try to use alien to convert that package from
>  > this "FC6" distribution (if it is a Linux disto) into a debian package?
>  >
>
> It's Fedora Core 6 I assume (a fairly old Fedora version, we're at
>  Fedora 9 now, having lost the 'Core').

Yes, it is an old Fedora Core 6.

>  htmlview is, as far as I can tell from recently looking into it, a
>  RedHat/Fedora script which does various convolutions to decide how to
>  try and display your HTML E-Mail (like it checks for X, then a GUI
>  browser, then a text mode browser, etc., etc.).

Does that mean it is not the mutt feature, rather the FC specific? How
can I make Debian work to display HTML emails the same way as FC6
does?

>  > What is the outcome of this command in a terminal:
>  >   echo $BROWSER
>  >
>  > Do you have an entry "text/html" in your /etc/mailcap or ~/.mailcap?
>  >
>
> Quite, much better without htmlview and doing it the 'user driven' way
>  that gives you what you specify rather than what the distribution
>  guesses you might want.

Would you please explain more what is the "user driver" way to achive that?

Thanks  Chris.

Kind Regards.


Re: htmlview

2008-05-10 Thread Chris G
On Sat, May 10, 2008 at 10:00:08AM +0200, Ionel Mugurel Ciobica wrote:
> On 10-05-2008, at 10h 26'28", hce wrote about "htmlview"
> > Hi,
> > 
> > I've set mutt in two machines, one in FC6 and another in Debian. The
> > FC6 installed htmlview, the FC6 mutt automatically launchs a brower
> > for viewing html emails. In Debian, I could not find htmlview package
> > for that feature. What package should I install in Debian to get
> > automatically launch a brower to view HTML emails like it in FC6?
> > 
> 
> What is "FC6"? Did you try to use alien to convert that package from
> this "FC6" distribution (if it is a Linux disto) into a debian package?
> 
It's Fedora Core 6 I assume (a fairly old Fedora version, we're at
Fedora 9 now, having lost the 'Core').

htmlview is, as far as I can tell from recently looking into it, a
RedHat/Fedora script which does various convolutions to decide how to
try and display your HTML E-Mail (like it checks for X, then a GUI
browser, then a text mode browser, etc., etc.).

> What is the outcome of this command in a terminal:
>   echo $BROWSER
> 
> Do you have an entry "text/html" in your /etc/mailcap or ~/.mailcap?
> 
Quite, much better without htmlview and doing it the 'user driven' way
that gives you what you specify rather than what the distribution
guesses you might want.

-- 
Chris Green


Re: htmlview

2008-05-10 Thread Ionel Mugurel Ciobica
On 10-05-2008, at 10h 26'28", hce wrote about "htmlview"
> Hi,
> 
> I've set mutt in two machines, one in FC6 and another in Debian. The
> FC6 installed htmlview, the FC6 mutt automatically launchs a brower
> for viewing html emails. In Debian, I could not find htmlview package
> for that feature. What package should I install in Debian to get
> automatically launch a brower to view HTML emails like it in FC6?
> 

What is "FC6"? Did you try to use alien to convert that package from
this "FC6" distribution (if it is a Linux disto) into a debian package?

What is the outcome of this command in a terminal:
  echo $BROWSER

Do you have an entry "text/html" in your /etc/mailcap or ~/.mailcap?

Ionel