On 2000.09.27, in <[EMAIL PROTECTED]>,
"Byrial Jensen" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 26, 2000 at 09:08:23 -0500, David Champion wrote:
> > Me, too. I take a different approach: I have a short wrapper script
> > that I use for invoking mutt. It sets LANG, then returns LC_COLLAT
On Tue, Sep 26, 2000 at 09:08:23 -0500, David Champion wrote:
> Me, too. I take a different approach: I have a short wrapper script
> that I use for invoking mutt. It sets LANG, then returns LC_COLLATE to
> C so that sorting works correctly. :)
Mutt disregards the setting of LC_COLLATE and alwa
Submitted 26-Sep-00 by Dave Ewart:
> Can you post a "mutt -v" of both a working and a non-working build? Or
> are they definitely the same?
I no longer have the broken 1.3.7 rpm, but I haven't changed any
configuration options in my spec file since 1.3.5. This is mutt -v on my
1.3.8 build:
Mut
On 2000.09.26, in <[EMAIL PROTECTED]>,
"Lars Hecking" <[EMAIL PROTECTED]> wrote:
>
> Example: in general, I prefer a C locale, but occasionally I do need
> certain non-ascii characters. So here's what I am using:
>
> $ grep LC_ ~/.muttrc
> set editor="LC_CTYPE=en_IE.ISO8859-15 vi"
> se
On Tue, Sep 26, 2000 at 09:38:49AM +0100, Dave Ewart wrote:
[..]
> I'd appreciate any insights as to why my posting got no response!
[..]
I seem to recall I grumbled about a similar thing awhile back (also
development series), and nothing anyone suggested worked for me. So I
suffer through it whe
On Tuesday, 26.09.2000 at 16:11 +0200, Thomas Roessler wrote:
> On 2000-09-26 14:48:35 +0100, Dave Ewart wrote:
>
> > I think my problem is with the Mutt internal pager not displaying stuff
> > right, since all other aspects involve using the editor Vim, and
> > characters display correctly. Yo
On 2000-09-26 14:48:35 +0100, Dave Ewart wrote:
> I think my problem is with the Mutt internal pager not displaying stuff
> right, since all other aspects involve using the editor Vim, and
> characters display correctly. Your external pager will mean that the
> internal pager is never used.
> G
On Tue, Sep 26, 2000 at 02:46:21PM +0100, Dave Ewart wrote:
> My feeling is that quite a large
> number of people _are_ using the development versions, though ...
Just because many people use a development version it doesn't follow that
they don't report
On Tuesday, 26.09.2000 at 11:34 +0100, Lars Hecking wrote:
> Dave Ewart writes:
> > On Tuesday, 26.09.2000 at 11:01 +0100, Lars Hecking wrote:
> >
> > > > e.g. the UK pound sign, £ (don't know how that'll appear for
> > > > most of you) appears as \243 (that's backslash, 2, 4, 3).
> > >
> > >
On Tuesday, 26.09.2000 at 13:08 +0200, Byrial Jensen wrote:
> On Tue, Sep 26, 2000 at 09:38:49 +0100, Dave Ewart wrote:
> > I'd appreciate any insights as to why my posting got no response!
>
> Well, one of the reasons could be that you post about problems with
> Mutt 1.3.x here at the mutt-user
On Tue, Sep 26, 2000 at 09:38:49 +0100, Dave Ewart wrote:
> I'd appreciate any insights as to why my posting got no response!
Well, one of the reasons could be that you post about problems with
Mutt 1.3.x here at the mutt-users list. The 1.3.x series are
development versions which are not conside
Dave Ewart writes:
> On Tuesday, 26.09.2000 at 11:01 +0100, Lars Hecking wrote:
>
> > > e.g. the UK pound sign, £ (don't know how that'll appear for most of
> > > you) appears as \243 (that's backslash, 2, 4, 3).
> >
> > Set your locale properly. If that doesn't help, compile with
> > --enable
On Tuesday, 26.09.2000 at 11:01 +0100, Lars Hecking wrote:
> > e.g. the UK pound sign, £ (don't know how that'll appear for most of
> > you) appears as \243 (that's backslash, 2, 4, 3).
>
> Set your locale properly. If that doesn't help, compile with
> --enable-locales-fix.
Thanks for the sug
> e.g. the UK pound sign, £ (don't know how that'll appear for most of
> you) appears as \243 (that's backslash, 2, 4, 3).
Set your locale properly. If that doesn't help, compile with
--enable-locales-fix.
On Tuesday, 26.09.2000 at 02:31 -0700, Anton Graham wrote:
> Submitted 26-Sep-00 by Dave Ewart:
> > I find it hard to believe that either of those explanations is true.
>
> It hits me intermittently, yes on some builds, not on others. So I
> don't have a guaranteed fix. I can't even tell you w
Submitted 26-Sep-00 by Dave Ewart:
> I find it hard to believe that either of those explanations is true.
It hits me intermittently, yes on some builds, not on others. So I don't
have a guaranteed fix. I can't even tell you what makes it happen, since I
use the same options for every build (I b
On Tuesday, 26.09.2000 at 20:13 +1100, raf wrote:
> Dave Ewart wrote:
>
> > I posted this question yesterday and have had no replies or
> > follow-ups. Does that mean that no-one else has this problem? Or
> > that loads of people have the problem and they can't solve it
> > either?? I find it
Dave Ewart wrote:
> I posted this question yesterday and have had no replies or follow-ups.
> Does that mean that no-one else has this problem? Or that loads of
> people have the problem and they can't solve it either?? I find it hard
> to believe that either of those explanations is true.
>
>
I posted this question yesterday and have had no replies or follow-ups.
Does that mean that no-one else has this problem? Or that loads of
people have the problem and they can't solve it either?? I find it hard
to believe that either of those explanations is true.
I'd appreciate any insights as
19 matches
Mail list logo
