Hi Ken,
> Let's say in a hypothetical future we support IMAP. That means that
> nearly every command would take a whole pile of arguments like
> -initialtls, -host, -port, -sasl, and more. Obviously changing your
> profile for every nmh command would be awful. So there should be some
> way of h
Hi David,
rfg wrote:
> > All these in combination you end with a reasonable reply to HTML
> > emails. The downside is that you don't get to keep the original
> > email unless you make a copy of it and it's fairly hacky.
>
> Thanks for all the tips, but this is a non-starter for me. I need to
> p
Hi,
rfg wrote:
> I have trouble believe that in this day and age, when we have had
> REALLY widespread use of HTML for around a couple of decades now, that
> there are still -zero- tools tyat can quicky render HTML into plain
> text without mucking it up somehow.
I found https://github.com/jaytay
Hi Ken,
> > Here is what I have set. is this what you are talking about? Or do
> > I need to fiddle sonmething else entirely?
> >
> > % env | fgrep LOCALE
> > XTERM_LOCALE=en_US.UTF-8
>
> Yeah, that's correct.
Is it? That's only xterm(1)'s locale. I think rfg should show us the
output of
In message <20190707172213.aeaff21...@orac.inputplus.co.uk>,
Ralph Corderoy wrote:
>> > Here is what I have set. is this what you are talking about? Or do
>> > I need to fiddle sonmething else entirely?
>> >
>> > % env | fgrep LOCALE
>> > XTERM_LOCALE=en_US.UTF-8
>>
>> Yeah, that's correct
Ralph writes:
> What if mhfixmsg could also append a new text/plain after the existing
> one, i.e. with a rank that's `better quality'. (Assuming RFCs allow two
> multipart/alternative with the same MIME type.)
That's a good idea. (My read of RFC 2045 is that it is allowed.)
Though in this cas
Date:Sun, 07 Jul 2019 12:56:13 -0700
From:"Ronald F. Guilmette"
Message-ID: <41320.1562529...@segfault.tristatelogic.com>
| But to answer Ralph's inquiry...
|
|
| LANG=en_US.UTF-8
| LC_CTYPE="en_US.UTF-8"
| LC_COLLATE="en_US.UTF-8"
| LC_TIME="en_US.UTF-8
Robert writes:
> Date:Sun, 07 Jul 2019 12:56:13 -0700
> From:"Ronald F. Guilmette"
> Message-ID: <41320.1562529...@segfault.tristatelogic.com>
>
> | But to answer Ralph's inquiry...
> |
> |
> | LANG=en_US.UTF-8
> | LC_CTYPE="en_US.UTF-8"
> | LC_COLLATE="en
Date:Sun, 07 Jul 2019 21:43:37 -0400
From:David Levine
Message-ID: <9828-1562550217.965...@xegg.pdiv.zhwy>
| That looks like the output of locale(1) rather than variable
| assignments.
Ah yes - even though that's what Ralph asked for, I didn't bother
to imagine
In message <13507.1562541...@jinx.noi.kre.to>, you wrote:
>Date:Sun, 07 Jul 2019 12:56:13 -0700
>From:"Ronald F. Guilmette"
>Message-ID: <41320.1562529...@segfault.tristatelogic.com>
>
> | But to answer Ralph's inquiry...
> |
> |
> | LANG=en_US.UTF-8
> | LC_CTYPE
Date:Sun, 07 Jul 2019 19:39:47 -0700
From:"Ronald F. Guilmette"
Message-ID: <42579.1562553...@segfault.tristatelogic.com>
| I confess I have and did explicitly set within my personal .login file
| thusly:
|
|setenv LANG en_US.UTF-8
That should be fine (I
11 matches
Mail list logo