Derek's message verified here.
Both of Ian's test messages verified here.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc
Description: PGP
On Sat, Oct 27, 2018 at 10:25:47AM -0700, Ian Zimmerman wrote:
> On 2018-10-25 13:06, Derek Martin wrote:
>
> > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
>
> Oh, I feel the itch again. Ow-ow, it's unbearable! I must scratch,
>
> Has anyone tried to verify Derek's G
On 2018-10-25 13:06, Derek Martin wrote:
> Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
Oh, I feel the itch again. Ow-ow, it's unbearable! I must scratch,
Has anyone tried to verify Derek's GPG signature on his message?
--
Please don't Cc: me privately on mailing li
On Thu, Oct 25, 2018 at 06:14:18PM +0100, Nuno Silva wrote:
> > Also, depending on exactly why you're doing this multi-locale stuff,
> > an even better solution may be to let Mutt's send_charset handle it
> > for you.
[...]
> But, if I understood the purpose of send_charset correctly, it only
> a
On 2018-10-25, Derek Martin wrote:
> On Thu, Oct 25, 2018 at 11:11:52AM -0500, Derek Martin wrote:
>> On Thu, Oct 25, 2018 at 12:53:43PM +0100, Nuno Silva wrote:
>> > When I use emacsclient, the interface locale is not broken: the terminal
>> > I/O encoding is correctly set from the locale. The on
On Thu, Oct 25, 2018 at 11:11:52AM -0500, Derek Martin wrote:
> On Thu, Oct 25, 2018 at 12:53:43PM +0100, Nuno Silva wrote:
> > When I use emacsclient, the interface locale is not broken: the terminal
> > I/O encoding is correctly set from the locale. The only difference (that
> > I know of) is th
On Thu, Oct 25, 2018 at 12:53:43PM +0100, Nuno Silva wrote:
> When I use emacsclient, the interface locale is not broken: the terminal
> I/O encoding is correctly set from the locale. The only difference (that
> I know of) is that Emacs will use utf8 to read/write files. If this
> should match the
On 2018-10-24, Derek Martin wrote:
> On Tue, Oct 23, 2018 at 10:31:45PM +0100, Nuno Silva wrote:
>> On 2017-10-12, nunojsi...@ist.utl.pt wrote:
>>
>> > Recently, I have tried to use mutt on a non-utf8 terminal. Everything
>> > works as expected in an utf8 environment, but when I compose new e-ma
On 2018-10-24, Ian Zimmerman wrote:
> On 2018-10-23 22:31, Nuno Silva wrote:
>
>> So far I did not find a way to change this on the mutt side, but I made
>> a new major mode for mutt messages in Emacs (the editor I use with
>> mutt), with a hook that changes the file encoding to latin1 if the file
On Tue, Oct 23, 2018 at 10:31:45PM +0100, Nuno Silva wrote:
> On 2017-10-12, nunojsi...@ist.utl.pt wrote:
>
> > Recently, I have tried to use mutt on a non-utf8 terminal. Everything
> > works as expected in an utf8 environment, but when I compose new e-mails
> > in a latin1/ISO-8859-1 terminal, m
On 2018-10-23 22:31, Nuno Silva wrote:
> So far I did not find a way to change this on the mutt side, but I made
> a new major mode for mutt messages in Emacs (the editor I use with
> mutt), with a hook that changes the file encoding to latin1 if the file
> was opened in a latin1 terminal and Emac
On 2017-10-12, nunojsi...@ist.utl.pt wrote:
> Recently, I have tried to use mutt on a non-utf8 terminal. Everything
> works as expected in an utf8 environment, but when I compose new e-mails
> in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
> same encoding as the terminal,
Hello,
Recently, I have tried to use mutt on a non-utf8 terminal. Everything
works as expected in an utf8 environment, but when I compose new e-mails
in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
same encoding as the terminal, while my text editor will save the file
in u
13 matches
Mail list logo
