GNU bug report logs -
#71081
30.0.50; shell-command-on-region outputs boilerplate text on Windows
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> posteo.net>
Date: Mon, 20 May 2024 18:34:01 UTC
Severity: normal
Tags: notabug
Found in version 30.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#71081: 30.0.50; shell-command-on-region outputs boilerplate text on Windows
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 71081 <at> debbugs.gnu.org.
--
71081: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71081
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: dmitry <at> gutov.dev, 71081 <at> debbugs.gnu.org, matt <at> excalamus.com
> Date: Thu, 23 May 2024 14:36:22 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> more over, on Linux, different shells have different behaviors wrt
> >> input/command argument/script file).
> >
> > Same on Windows. Try PowerShell some day. Does it mean we need to
> > document all of that in our documentation?
>
> It would be nice, yes. Without details - just point that there is a
> difference. Maybe in the "41.3 Creating a Synchronous Process" section
> of the manual.
Done, and closing the bug.
[Message part 3 (message/rfc822, inline)]
Hello,
On Linux, if I put
echo foo
into scratch, select it, and run M-x shell-command-on-region sh,
I get "foo" in echo area.
However, on Windows, the result of M-x shell-command-on-region cmdproxy is
Microsoft Windows [Version 10.0.19045.2251]
(c) Microsoft Corporation. All rights reserved.
c:\Users\johndoe\Org>echo foo
foo
I expected just "foo".
Original bug report:
https://list.orgmode.org/orgmode/CACjq+cy8G+EkMgSwr5KWNbN7jjLE3tzqKwbQiTy84ZvJsumMwQ <at> mail.gmail.com/
AFAIU, the culprit is how cmdproxy handles piped input:
cmdproxy -c 'echo foo' works fine, outputting "foo".
However (in powershell) echo 'echo foo' | cmdproxy yields the above
verbose text - all in stdout.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
This bug report was last modified 1 year and 54 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.