unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmitry@gutov.dev, 71081@debbugs.gnu.org, matt@excalamus.com
Subject: bug#71081: 30.0.50; shell-command-on-region outputs boilerplate text on Windows
Date: Thu, 23 May 2024 12:06:25 +0000	[thread overview]
Message-ID: <87cypcybpa.fsf@localhost> (raw)
In-Reply-To: <86zfsh6gpp.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> > The easiest way of solving this conundrum is to create a temporary
>> > batch file, insert all the commands into it, with the first line being
>> >
>> >   @echo off
>> >
>> > and then submit the name of that batch file to the Windows shell as
>> > the sole command-line argument after shell-command-switch.  So my
>> > recommendation is to do just that, on Windows.
>> 
>> May it be something you also want to do for `shell-command-on-region'?
>
> No, because in general the region is some text we want to give a
> program as input.  The usual "program" in these cases is not the
> shell, but some program that gets the text and processes it in some
> way.
>
> So in most "usual" uses of shell-command-on-region, going through a
> batch file is an unnecessary overhead.

Clear. I am not a big user of shell-command-on-region.

Then, what about something like

(shell-command-to-string "echo foo\necho bar")

On Linux, it yields
"foo
bar"

On Windows, it yields

"foo"

-- 
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>





  reply	other threads:[~2024-05-23 12:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 18:34 bug#71081: 30.0.50; shell-command-on-region outputs boilerplate text on Windows Ihor Radchenko
2024-05-20 18:59 ` Eli Zaretskii
2024-05-21 20:18   ` Dmitry Gutov
2024-05-22  2:30     ` Eli Zaretskii
2024-05-22 11:45       ` Ihor Radchenko
2024-05-22 13:33         ` Eli Zaretskii
2024-05-22 14:26           ` Ihor Radchenko
2024-05-22 14:53             ` Eli Zaretskii
2024-05-23 12:06               ` Ihor Radchenko [this message]
2024-05-23 13:37                 ` Eli Zaretskii
2024-05-23 14:00                   ` Ihor Radchenko
2024-05-23 14:14                     ` Eli Zaretskii
2024-05-23 14:36                       ` Ihor Radchenko
2024-05-25 10:03                         ` Eli Zaretskii
2024-05-25 10:03                         ` Eli Zaretskii

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=87cypcybpa.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=71081@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=matt@excalamus.com \
    /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).