From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Third <alan@idiocy.org>
Cc: Philipp <p.stephani2@gmail.com>,
51832@debbugs.gnu.org, tor.a.s.kringeland@ntnu.no
Subject: bug#51832: Piping unicode text in `shell-command'
Date: Sun, 14 Nov 2021 14:41:38 +0100 [thread overview]
Message-ID: <87v90u7t2l.fsf@gnus.org> (raw)
In-Reply-To: <YZEBqFv8o4sjYKtJ@idiocy.org> (Alan Third's message of "Sun, 14 Nov 2021 12:31:36 +0000")
Alan Third <alan@idiocy.org> writes:
> I've attached a patch that may do something towards preventing this
> problem but ultimately this is a convenience to give a best guess at
> choosing the correct dictionary, date format, etc. If we can't easily
> fix it then we can drop it and tell people to set it in their init.el
> themselves.
That didn't fix the issue for me, I'm afraid -- with that patch, LANG is
still the invalid en_NO.UTF-8 for me.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-11-14 13:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 3:10 bug#51832: Piping unicode text in `shell-command' Tor Kringeland
2021-11-14 7:26 ` Eli Zaretskii
2021-11-14 7:53 ` Lars Ingebrigtsen
2021-11-14 8:13 ` Eli Zaretskii
2021-11-14 8:18 ` Lars Ingebrigtsen
2021-11-14 8:25 ` Eli Zaretskii
2021-11-14 9:19 ` Lars Ingebrigtsen
2021-11-14 9:32 ` Lars Ingebrigtsen
2021-11-14 9:46 ` Lars Ingebrigtsen
2021-11-14 10:31 ` Eli Zaretskii
2021-11-14 10:41 ` Philipp
2021-11-14 10:56 ` Eli Zaretskii
2021-11-14 11:20 ` Lars Ingebrigtsen
2021-11-14 11:48 ` Philipp
2021-11-14 12:16 ` Eli Zaretskii
2021-11-14 12:31 ` Alan Third
2021-11-14 13:41 ` Lars Ingebrigtsen [this message]
2021-11-14 14:23 ` Philipp
2021-11-14 14:28 ` Lars Ingebrigtsen
2021-11-14 15:20 ` Alan Third
2021-11-14 15:29 ` Lars Ingebrigtsen
2021-11-16 20:52 ` Alan Third
2022-09-20 13:24 ` Lars Ingebrigtsen
2021-11-14 15:01 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v90u7t2l.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51832@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=p.stephani2@gmail.com \
--cc=tor.a.s.kringeland@ntnu.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).