unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tor.a.s.kringeland@ntnu.no, 51832@debbugs.gnu.org, alan@idiocy.org
Subject: bug#51832: Piping unicode text in `shell-command'
Date: Sun, 14 Nov 2021 10:19:13 +0100	[thread overview]
Message-ID: <87lf1r857y.fsf@gnus.org> (raw)
In-Reply-To: <83k0hbuosm.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Nov 2021 10:25:29 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Maybe we set some locale-related environment variable, and that was
> confuses pbcopy when it is run from Emacs?

I've now followed the call tree, and we end up doing:

(call-process-region (point) (point) shell-file-name nil
                     (current-buffer) nil shell-command-switch
                     "echo foo😀bar | pbcopy")

And that fails, too.  So it's not something that shell-command sets up
(if it's a locale-related thing).

Hm...  Oh!  I thought the original report said that this worked if run
under M-x shell.  But it doesn't -- I get the same garbled selection.
(And it works fine in a shell outside Emacs.)

So it could indeed be a locale setting in Emacs that's making pbcopy do
the wrong thing. 

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-11-14  9:19 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 [this message]
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
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=87lf1r857y.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=51832@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.org \
    --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).