0n Thu, Jul 05, 2007 at 10:00:12PM -0600, Vincent Beffara wrote:
>Try adding the following line to your .muttrc (or replacing the
>ppropriate line):
>
>set editor="vim -X"
>
>Long version: vim by default (or not) tries to connect to the X server
>to enable client/s
> Hi all,
>
> I use vim as $editor with Mutt 1.5.16. When I use vim with eterm(1) on FreeBSD
> CURRENT it opens instantaneously, however, occasionally I use Putty on Windows
> and ssh(1) into FreeBSD and vim literally takes 20 seconds to open. $TERM is
> set to xterm.
>
> Can anyone recommend wh
Hi all,
I use vim as $editor with Mutt 1.5.16. When I use vim with eterm(1) on FreeBSD
CURRENT it opens instantaneously, however, occasionally I use Putty on Windows
and ssh(1) into FreeBSD and vim literally takes 20 seconds to open. $TERM is
set to xterm.
Can anyone recommend what could be wrong
On Wed, Jul 04, 2007 at 06:24:08PM +0100, Chris G wrote:
> pattern.o: In function `mutt_which_case':
> /home/isbd/build/mutt-1.5.16/pattern.c:150: undefined reference to
> `iswalpha'
> /home/isbd/build/mutt-1.5.16/pattern.c:150: undefined reference to
> `iswupper'
Probably would work
On Wed, Jul 04, 2007 at 10:13:27AM -0700, Breen Mullins wrote:
> * Breen Mullins <[EMAIL PROTECTED]> [2007-07-04 10:03 -0700]:
> >Thanks for the hints on charset-hooks - I tried them but it didn't help.
>
> Aargh. Cancel that - I just checked my work, corrected the error - and
> the problem messa
* Derek Martin on Wednesday, July 04, 2007 at 15:08:47 -0400:
> If you've ever taken a computer science class at a school
Never. I went to school when there weren't any computers around;
thank God those days (I mean school days) are long gone ...
I'm blissfully uneducated re technical stuff (I go
Hi,
* Chris G [07-07-04 18:24:08 +0100] wrote:
uname -a gives:-
FreeBSD newred.gradwell.net 4.8-STABLE FreeBSD 4.8-STABLE #1
./configure seems to work OK (using --prefix=$HOME) but I needed a specific
--with-homespool as well.
However although it compiles (with *lots* of warnings about t
