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
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
>
> > > 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
13 matches
Mail list logo
