Hello,
Once more i found a behaviour in my Mutt-1.20. (on Ubuntu.Linux) that puzzles
me. Any Pointers as to which way to look will help.
"CTRL-Z" suspends mutt but "fg" doesn't seem to work. Mutt displayes but
pressing
keys obviously still refers to the terminal below.
I hadn't noticed this bef
Hi,
Rocco Rutte wrote on 24.06.09:
> > The apt-get command installed elinks on my system and now opening html-mails
> > via the "v"-command starts elinks instead of w3m like before. I wonder where
> > this is being determined. My mailcap has entries for w3m, elinks and lynx in
> > this order.
>
Hi,
* Jan-Herbert Damm wrote:
> The apt-get command installed elinks on my system and now opening html-mails
> via the "v"-command starts elinks instead of w3m like before. I wonder where
> this is being determined. My mailcap has entries for w3m, elinks and lynx in
> this order.
See $mailcap_pa
Hello all,
with your hints I was able to build Mutt-1.20. successfully. I chickened out
by running "apt-get build-dep mutt" as indicated in
http://wiki.mutt.org/?MuttFaq/Charset.
The apt-get command installed elinks on my system and now opening html-mails
via the "v"-command starts elinks instead
Hi,
* Jan-Herbert Damm wrote:
> Since i also have strange encoding behaviour in Mutt-1.18. (i may not use
> german umlauts in muttrc else running into trouble) i hope to find a common
> root to these issues.
If nothing else helps you can tell mutt in what encoding your config
files are, see the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, June 18 at 11:28 PM, quoth Jan-Herbert Damm:
> This is particularly disturbing because my Mutt-1.20. hat great
> problems displaying numerous characters (such as the lines showing
> the threads and german umlauts etc.) But ":set ?chars
Hello,
Thanks for explanations!
I tried another build and found that my switches revealed more problems that i
want to gnaw on for a while.
> >+HAVE_LANGINFO_CODESET
>
> Literally, this means that your system has the langinfo.h header and
> the nl_langinfo(CODESET) function is available as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, June 18 at 05:38 PM, quoth Jan-Herbert Damm:
>I found quite a few discrepancies comparing mutt -v output.
>
>These are the compiler-flags used in Mutt-1.18.-ubuntu-build but not used in
>my Mutt-1.20.-home-build and of which i don't know
Hi,
Rocco Rutte wrote on 18.06.09:
>
> * Jan-Herbert Damm wrote:
> At first it can be tricky to get all the configure flags right. You can
> compare the output of mutt -v of both installed versions, check for
> differences and ask here again if you can't figure out where a
> flag/option comes fro
Hi,
* Jan-Herbert Damm wrote:
> I am glad i followed this advice. Thanks Rocco! It turns out i have to resolve
> some issues. Encoding and gpg don't work as expected. I will do some
> investigation.
At first it can be tricky to get all the configure flags right. You can
compare the output of mut
Hello,
Rocco Rutte wrote on 16.06.09:
> Jan-Herbert Damm wrote:
>
> > I would like to try Mutt 1.5.20
>
> I usually choose ~/opt/mutt/ so that I can easily install without sudo and
> deinstall with rm.
I am glad i followed this advice. Thanks Rocco! It turns out i have to resolve
some issu
Hi,
* Jan-Herbert Damm wrote:
> I would like to try it out. To be safe i want to keep my working Mutt 1.5.18
> in /usr/bin and install Mutt 1.5.20 in /usr/local/bin.
> "./configure" (without any options) and "make" went well.
> Can i safely "sudo make install"?
Please look at the --prefix optio
Hi,
* Bertrand Janin wrote:
> The correct parameter seems to be $ssl_verify_host not $ssl_verify_hostname.
Fixed, thanks.
Rocco
Hello,
Adam Wellings wrote on 15.06.09:
> >
> > > > Mutt 1.5.20 is out at the usual locations.
> It's on Sourceforge
Thanks. Now i found it.
I would like to try it out. To be safe i want to keep my working Mutt 1.5.18
in /usr/bin and install Mutt 1.5.20 in /usr/local/bin.
"./configure" (wi
On Monday, 15 June 2009 at 10:00, Jan-Herbert Damm wrote:
> Hello,
>
> > > Mutt 1.5.20 is out at the usual locations.
>
> please, where are these locations?
> i couldn't find this version on mutt.org.
> maybe just cvs?
Sorry, the web site hasn't been updated yet, but the locations there
are c
Brendan Cully wrote :
> + $ssl_verify_hostname controls whether mutt will accept certificates whose
> host names do not match the host name in the folder URL.
The correct parameter seems to be $ssl_verify_host not $ssl_verify_hostname.
Bertrand
On Mon, 15 Jun 2009, Gerard Robin wrote:
> On Mon, Jun 15, 2009 at 10:25:38AM +0800, bill lam wrote:
> >Date: Mon, 15 Jun 2009 10:25:38 +0800
> >From: bill lam
> >To: mutt-users@mutt.org
> >Subject: Re: [ANNOUNCE] 1.5.20 released
> >
> >Many thanks for detai
Gerard Robin wrote:
> Did you make a debian package ?
> If yes, can you show your file control ?
Why not just check out the Debian package files from
http://git.debian.org/?p=pkg-mutt/mutt.git;a=summary ?
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~
On Mon, Jun 15, 2009 at 10:25:38AM +0800, bill lam wrote:
Date: Mon, 15 Jun 2009 10:25:38 +0800
From: bill lam
To: mutt-users@mutt.org
Subject: Re: [ANNOUNCE] 1.5.20 released
Many thanks for detail steps and explanation. I compiled and am now
using the new mutt.
Did you make a debian package
>
> > > Mutt 1.5.20 is out at the usual locations.
>
> please, where are these locations?
> i couldn't find this version on mutt.org.
> maybe just cvs?
>
It's on Sourceforge:
http://sourceforge.net/project/showfiles.php?group_id=195
cheers,
Adam
--
"...one cannot be angry when one look
Hello,
> > Mutt 1.5.20 is out at the usual locations.
please, where are these locations?
i couldn't find this version on mutt.org.
maybe just cvs?
jan
Many thanks for detail steps and explanation. I compiled and am now
using the new mutt.
--
regards,
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
On Monday, 15 June 2009 at 09:25, bill lam wrote:
> On Sun, 14 Jun 2009, Brendan Cully wrote:
> > Silly autoconf. Try:
> > autoreconf -i
> > ./config.status --recheck
> > ./config.status
>
> I tried
>
> $ autoconf -i ./config.status
> /usr/bin/m4:aclocal.m4:917: cannot open `m4/libgnutls.m4': No
On Sun, 14 Jun 2009, Brendan Cully wrote:
> Silly autoconf. Try:
> autoreconf -i
> ./config.status --recheck
> ./config.status
I tried
$ autoconf -i ./config.status
/usr/bin/m4:aclocal.m4:917: cannot open `m4/libgnutls.m4': No such file or
directory
autom4te: /usr/bin/m4 failed with exit status
On Monday, 15 June 2009 at 08:46, bill lam wrote:
> > Mutt 1.5.20 is out at the usual locations. This release contains an
>
> After hg pull and update. It failed to make or even make clean with error
> message.
>
> make: *** No rule to make target `m4/libgnutls.m4', needed by
> `Makefile.in'
>
>
> Mutt 1.5.20 is out at the usual locations. This release contains an
After hg pull and update. It failed to make or even make clean with error
message.
make: *** No rule to make target `m4/libgnutls.m4', needed by
`Makefile.in'
I can build earlier 1.5.19 version without problem. Any idea how to
26 matches
Mail list logo
