From: Bryan Whitehead <driver@megahappy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] vim-in-pine problem
Date: Mon, 23 Oct 2006 20:11:43 -0700 [thread overview]
Message-ID: <453D846F.3050207@megahappy.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0610210949560.18835@jmaa.math.ist.utl.pt>
For me it was already having known all the pine keys... mutt isn't that
much better to justify months of readjusting to a new email reader...
Jorge Almeida wrote:
> On Sat, 21 Oct 2006, Philip Webb wrote:
>
>>> I don't really remember why I didn't stick with mutt,
>>> but I know there were some reasons: colors? difficult to configure?
>>
>> Yes, you need to read 'man muttrc' & set up ~/.muttrc to your tastes.
>>
> There was something else...Asking for password too many times?
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-10-24 3:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:09 [gentoo-user] vim-in-pine problem Jorge Almeida
2006-10-20 19:22 ` Willie Wong
2006-10-20 23:21 ` Jorge Almeida
2006-10-21 3:40 ` Willie Wong
2006-10-21 7:35 ` Jorge Almeida
2006-10-21 4:28 ` Philip Webb
2006-10-21 7:45 ` Jorge Almeida
2006-10-21 8:05 ` Philip Webb
2006-10-21 8:50 ` Jorge Almeida
2006-10-24 3:11 ` Bryan Whitehead [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453D846F.3050207@megahappy.net \
--to=driver@megahappy.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox