Re: [ANNOUNCE] 1.5.20 released
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 before which i find surprising since i often use CRTL-Z. Mutt-18.1 custom ubuntu-binary doesn't show this problem. jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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. > > See $mailcap_path. I'm almost certain mutt uses the first match in the > first file in that setting... which maybe is a system-wide file in your > case. If ~/.mailcap isn't the first one, use it was the first entry but didn't exist. The first existing entry was /etc/mailcap but making a file .mailcap with just the line concerning w3m does work (!) jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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_path. I'm almost certain mutt uses the first match in the first file in that setting... which maybe is a system-wide file in your case. If ~/.mailcap isn't the first one, use set mailcap_path="~/.mailcap:$mailcap_path" to prepend it. Rocco
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 of w3m like before. I wonder where this is being determined. My mailcap has entries for w3m, elinks and lynx in this order. BTW: encoding mysteries haven't all been solved but i am at peace for now. Applying this suggestion (from the mentioned link) to .vimrc was damaging. set encoding& " terminal charset: follows current locale set termencoding= set fileencodings= " charset auto-sensing: disabled set fileencoding& " auto-sensed charset of current buffer It resulted in a replacement of lots of umlauts with questionmarks in innoscent files(!) jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 end of this section: http://dev.mutt.org/doc/manual.html#muttrc-syntax Rocco
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
-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 ?charset" renders > "utf-8". > > 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. Ahh - in that case, I think you probably want to read http://wiki.mutt.org/?MuttFaq/Charset. It explains things reasonably well, and contains a great test (see "How can I check if locales work before I blame Mutt for it?"). I bet that solves your problem for you. ~Kyle - -- Blessed are they who can laugh at themselves for they shall never cease to be amused. -- Unknown -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKOrslAAoJECuveozR/AWeZHYP/jYMCC6y9bx2moRboWsHy8N9 fPqgl0VYpXO00dT7ePziib3d/KFJ5ijwuHzabFz3ereojpe6z+aGYYPDEuBJwmRx hWvCpb6QjNEE/JC5K3+ppFoU8QgQtjW8Y/6AicCQlYaXrosnQM2OiAxpQGoaFx10 XrBJvKs0GkeJnlxggXWLIo7jdLxJOge3K0tOwYSgUrAHuTSJxURlNg2bYN0Zq7KR G279msfW35CxPLOP6LRJG69R5I4vL7slLAImKoSg2/Q2ZROiacG2PYw4SCPP9WPS UgBeg/+6CqinZ62j4jksLqrAiJC7yCR/gBsARmLl72pACQk7bhNw4gS50zgv2oCq l/v7iTWL5wpZNvGayHjM7Omsfqg5nvilBhEV4wUZ8QdLqsCqRUtguuWTmF116m4d CxmVr1bMHhFZwZqio9v2WNFVekcmTuxfJqg6hmisLvbbSRwxdCwxFKM+KkRY4aAh 9IKMx70FXqkhSiQ4R0FvFc6ABUkb9ifKu9jeUVedflTc9PoIZoLcUN9fRIP37yiL 6+5ijl4sxd8GGuP0uIejhcPY81dBofW6NCAl4eROuLeGEkD1t+UThTLlTajZ4t3E 1DgoZ98Ff+ZMAJOk52dmCcGjL0qv1haTMKZVaD7E0NbQWi1nRHE5yr0oFRjHxtWF EGFY8JZrqReZu6vP8Erh =qfj4 -END PGP SIGNATURE-
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 well. This allows > mutt to automatically detect the default charset the system wants to > use---without this ability, mutt is forced to assume some default > charset (namely ISO-8859-1). 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 ?charset" renders "utf-8". 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. I will report back when/if i find out more. greetings jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
-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 what configure-option they >are triggered by: > >+HAVE_GETADDRINFO This means that the system mutt was configured on (i.e. yours versus the Ubuntu build system) has the getaddrinfo() function available. Generally, I believe this is used primarily by mutt to decide whether it can support IPv6 (the getaddrinfo function is more flexible than other methods, and so can be used with IPv6). I don't believe that there is a configure argument you can use that forces this to be used or not. >+COMPRESSED This is a reference to the Ubuntu/Debian compressed-mbox patch. In essence, they use a patch that allows mutt to read a gzip'd mbox file. >+HAVE_LANGINFO_CODESET Literally, this means that your system has the langinfo.h header and the nl_langinfo(CODESET) function is available as well. This allows mutt to automatically detect the default charset the system wants to use---without this ability, mutt is forced to assume some default charset (namely ISO-8859-1). Again, there's no way to force mutt to use or not use this by passing arguments to configure; it relies entirely upon the localization features your computer supports. HTH, ~Kyle - -- Formal symbolic representation of qualitative entities is doomed to its rightful place of minor significance in a world where flowers and beautiful women abound. -- Albert Einstein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKOmOlAAoJECuveozR/AWef3QQAIB4b54At7dkIDlp4G3xUlIo tD1jY9GSaKBzsS/xJUfBUMZNUsLv6Zb1CzTQWVM29XwttTvBWkvwGkb1v5m7k3ZR ihD3U9sG9Y378wCIxSvZevMfpO/pb8KuTLhS89uaP3drEQz/TqmHkuLSr+E95Dgn 1uH0GR8SbaTAp7Qf63SZr198Szw1w5iIgE2bkaBs9sqo8JXS8L++ox6s8Aje4e3m Rm7JwIy6atlGM8n6zb8X+wIfCQBT5Rtr8iB1lQPozA3QtbeVqnKwqBguHGcE4MIB rtd7F1thkcxFeTjVyTvU8n2LTGfly39M60fKHYO3q4Oo2X3A9xxd7ECh0w/c3ju/ Jing/mS8uXqIWiLLqR23qgT1YOqwghaGaocxcaUxoyz/i/2/LJCEmgFQE4Ea3yxG UlDFZenEpqAwzTvaA5o9eej93JRU7ms5P+dd971PgAT+gBsQNMtFDOohlOitckNC Pl7R4d83y4o8lCawJUUVVDEVSqQRyxsMLnklz+yHATlRiUVzMp0we7a0Zlk32bAx BbhYbDr24skPi4k28r1IQ1YKg9kMLx2hHV8Scg8GnsVvzRNRWcH3a4NrBBhkbU/V B2iLFcAGURz5SNLZS1RmUtKl0yoECOXxJ0UjVtUzMwZOyeALoHNVO4RTK8JiN29Z mcpPeQkeUaZs5QXQOsVc =3Dtk -END PGP SIGNATURE-
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 from. 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 what configure-option they are triggered by: +HAVE_GETADDRINFO +COMPRESSED +HAVE_LANGINFO_CODESET jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 mutt -v of both installed versions, check for differences and ask here again if you can't figure out where a flag/option comes from. Rocco
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 issues. Encoding and gpg don't work as expected. I will do some investigation. It is my first manual install of mutt. The old version is apt-get installed. jan
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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 option for configure. I usually choose ~/opt/mutt/ so that I can easily install without sudo and deinstall with rm. You also might want to look at more options of configure --help to mimic your current version so you don't miss optional features you now have compiled in 1.5.18 (header cache, etc.) Rocco
Re: [ANNOUNCE] 1.5.20 released
Hi, * Bertrand Janin wrote: > The correct parameter seems to be $ssl_verify_host not $ssl_verify_hostname. Fixed, thanks. Rocco
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
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" (without any options) and "make" went well. Can i safely "sudo make install"? jan
Re: [ANNOUNCE] 1.5.20 released
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 correct: ftp://ftp.mutt.org/mutt/devel/mutt-1.5.20.tar.gz or via sourceforge. pgprTa5zRAchs.pgp Description: PGP signature
Re: [ANNOUNCE] 1.5.20 released
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
Re: [ANNOUNCE] 1.5.20 released
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 detail steps and explanation. I compiled and am now > >using the new mutt. > > Did you make a debian package ? > If yes, can you show your file control ? I just ./configure && make && make install. ;-) -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Re: [ANNOUNCE] 1.5.20 released
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 ~~ There are three ways to get something done: do it yourself, hire someone, or forbid your kids to do it. -- Monta Crane pgpdiss6IYdqq.pgp Description: PGP signature
Re: [ANNOUNCE] 1.5.20 released
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 ? If yes, can you show your file control ? Thanks. -- Gérard
Re: [mutt] Re: [ANNOUNCE] 1.5.20 released
> > > > 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 looks at a penguin." - John Ruskin
Re: [ANNOUNCE] 1.5.20 released
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
Re: [ANNOUNCE] 1.5.20 released
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
Re: [ANNOUNCE] 1.5.20 released
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 such file or > directory > autom4te: /usr/bin/m4 failed with exit status: 1 > > $ ls m4 > codeset.m4 funcdecl.m4 gettext.m4 gpgme.m4 iconv.m4 Makefile.am > README > curslib.m4 funcs.m4 glibc21.m4 gssapi.m4 lcmessage.m4 progtest.m4 > types.m4 > > Apparently that libgnutls.m4 is not inside hg repository. Where can I get > that file? Those were on separate lines because they were meant to be separate commands, issued one after the other. $ autoreconf -i $ ./config.status --recheck $ ./config.status libgnutls.m4 has been deliberately removed, but the build system needs to be hit on the head to figure that out. That's what the steps above do.
Re: [ANNOUNCE] 1.5.20 released
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: 1 $ ls m4 codeset.m4 funcdecl.m4 gettext.m4 gpgme.m4 iconv.m4 Makefile.am README curslib.m4 funcs.m4 glibc21.m4 gssapi.m4 lcmessage.m4 progtest.m4 types.m4 Apparently that libgnutls.m4 is not inside hg repository. Where can I get that file? Linux debian 2.6.26-2-amd64 #1 SMP Thu May 28 21:28:49 UTC 2009 x86_64 GNU/Linux -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Re: [ANNOUNCE] 1.5.20 released
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' > > I can build earlier 1.5.19 version without problem. Any idea how to > fix it? Silly autoconf. Try: autoreconf -i ./config.status --recheck ./config.status
Re: [ANNOUNCE] 1.5.20 released
> 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 fix it? -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
