[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using mutt ...



Well, I could also just use pine instead of mutt and have a much 
smaller learning curve with pine than I think I'll have creating a .muttrc 
file.

Actually, I thought that if I forced myself to use vi for my mail composer I 
would learn to use vi proficiently and then not have to open up more 
combersome programs when I'm trying to do simple things on the command line.

.... this is all part of my plan for "simplifying" my life by using more 
command line programs ...

Of course, if this doesn't work maybe I'll just get rid of my computer and 
become Amish instead ...  ; )

jburke.

On Friday 18 January 2002 12:40, you wrote:
> I like vim.  But, if it's not your thing, can't you use any editor with
> Mut?  I bet you could coax it to use pico or something.
>
>
> -----Original Message-----
> From: James L. Burke [mailto:jburke@jburke.com]
> Sent: Friday, January 18, 2002 11:20 AM
> To: silug-discuss@silug.org
> Subject: Using mutt ...
>
>
> Hello all,
>
> I've decided I'm interested in giving mutt a try as my mail reader.
> I've
> been MS Windows (TM) free for over 6 months now and I'm beginning to
> think I
> could manage my email much quicker if I didn't have to point and click
> so
> much.  Right now I'm using kmail and I've been relatively pleased with
> the
> results.  Nevertheless, I'd like to give mutt a try for a few weeks.
>
> Before I take this plunge, I thought I'd ask for some advice from the
> group.
>
> First, any general suggestion regarding mutt are welcome.
>
> Second ...
>
> I can already see a problem with the way my email is set up ... even
> though
> kmail uses the mbox format, kmail allows me to put folders inside other
> folders on the kmail screen.  This turns out to be one file and all the
> sub-folders and their contents seem to be ignored by mutt.  I can fix
> this by
> moving all these mail messages to their own kmail folder (mbox file) ...
> any
> better ideas?
>
> Also, is there a way to reduce the learning curve on .muttrc?  I'm
> reluctant
> to spend a lot of time creating a nifty .muttrc file and then decide
> mutt
> isn't going to get the job done for me ... suggestions?
>
> Lastly, same question with regard to mutt's compose screen ... vim.
> I've
> never spent the time to get as proficient with vi as I know I should be
> ...
> any suggested links or tutorials to learn vi/vim?  (I'm embarrassed to
> admit
> that all though I know there is already a tutorial for vi/vim on my box
> I
> haven't been able to get it to run yet ... suggestions?)
>
> Thanks,
>
> jburke (Jim not Jason - Jason obviously wouldn't be asking this question
> and
> I'd hate for anyone to think he'd somehow lost his mind and forgot how
> to use
> vi and mutt ...)   ; )
>
> -
> To unsubscribe, send email to majordomo@silug.org with
> "unsubscribe silug-discuss" in the body.

-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.