On 2008-05-30 07:55:02 +0200, Rocco Rutte wrote:
> And since OS X already comes with ncurses in /usr, I recommend not
> installing ncurses port at all so that you have only one ncurses and
> ncursesw installed...
This is IMHO a bad recommendation, at least for Mac OS X 10.4.* users.
The ncurse
Hi,
* André Berger wrote:
Progress here :)
MacPorts 1.600
The following ports are currently installed:
ncurses @5.6_0 (active)
ncursesw @5.6_1 (active)
Discussion on comp.mail.mutt led me to temporarily uninstall ncurses,
and my config.h got modified to
#define HAVE_NCURSES_H
* André Berger (2008-05-22):
> * Rocco Rutte (2008-05-22):
> > * André Berger wrote:
> >
> >> More testing shows the issue is related to "--enable-gpgme". A clean
> >> source with
> >
> >> ./configure --enable-gpgme && make all && ./mutt -n -F /dev/null -f
> >> ~/Mail/mbox
> >
> >> is enough. Wit
* André Berger on Thursday, May 22, 2008 at 13:42:53 +0200
> * Rocco Rutte (2008-05-22):
>> * André Berger wrote:
> [...]
>> Okay, since it's pager and index, it must be some header. The only thing
>> relevant to encoding/internationalization issues between 1.5.17 and 1.5.18
>> is that X-Label he
* Rocco Rutte (2008-05-22):
> * André Berger wrote:
>
>> More testing shows the issue is related to "--enable-gpgme". A clean
>> source with
>
>> ./configure --enable-gpgme && make all && ./mutt -n -F /dev/null -f
>> ~/Mail/mbox
>
>> is enough. With --enable-gpgme left out, it works, with all my
Hi,
* André Berger wrote:
More testing shows the issue is related to "--enable-gpgme". A clean
source with
./configure --enable-gpgme && make all && ./mutt -n -F /dev/null -f ~/Mail/mbox
is enough. With --enable-gpgme left out, it works, with all my
patches and configuration options appl
* Rocco Rutte (2008-05-22):
> * André Berger wrote:
[...]
> Okay, since it's pager and index, it must be some header. The only thing
> relevant to encoding/internationalization issues between 1.5.17 and 1.5.18
> is that X-Label headers now have to be RfC2047-encoded. Could that be the
> reason?
Hi,
* André Berger wrote:
Thanks for your attention!
LANG=en_US.UTF-8 # in bash
Character encoding: Unicode (UTF-8) # Mac OS X Terminal.app
Do Set LANG environment variable on startup # Mac OS Terminal.app
That's what I've guessed.
- where does that happen (pager, index, everywh
* Rocco Rutte (2008-05-22):
> * André Berger wrote:
>
>> since 1.5.18 (+nntp +compressed), I'm experiencing a strange problem.
>> Uppercase Umlauts (ÄÖÜ) and sz (ß) are displayed incorrectly, as
>> "?~D", "?~V", "?~\"; "?~_". Lowercase Umlauts are OK. This is for
>> example with "text/plain; charse
Hi,
* André Berger wrote:
since 1.5.18 (+nntp +compressed), I'm experiencing a strange problem.
Uppercase Umlauts (ÄÖÜ) and sz (ß) are displayed incorrectly, as
"?~D", "?~V", "?~\"; "?~_". Lowercase Umlauts are OK. This is for
example with "text/plain; charset=UTF-8; format=flowed" resp.
"text/
Hi there,
since 1.5.18 (+nntp +compressed), I'm experiencing a strange problem.
Uppercase Umlauts (ÄÖÜ) and sz (ß) are displayed incorrectly, as
"?~D", "?~V", "?~\"; "?~_". Lowercase Umlauts are OK. This is for
example with "text/plain; charset=UTF-8; format=flowed" resp.
"text/plain; charset=utf-
11 matches
Mail list logo