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 terminal encoding, then it *is* broken.
I suspected as much. The issue, as far as I can tell based on your description of things, is that the emacs *server* is running with a UTF-8 locale, which is why it is editing files in that locale, and you're connecting to it from a client that's running a different locale. That's definitely broken, as would be any such locale mismatch. Your hack may well work around it... but you should be very clear that you're doing something unexpected (and generally undesirable) which may well break in other ways later. That's what's called a gross hack. A likely better solution would be to run two instances of emacs server, one in each locale, and make mutt connect to the right one. But either way it comes down to the choice of running two different instances of emacs, or using a gross hack to avoid that. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgp_KyQrAdmHJ.pgp
Description: PGP signature
