unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Arash Esbati <arash@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: (Windows) Problems with processes on master branch
Date: Sat, 02 Mar 2024 13:16:10 +0100	[thread overview]
Message-ID: <867cikakxh.fsf@gnu.org> (raw)
In-Reply-To: <87sf19aoj1.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Fri, 01 Mar 2024 17:46:10 +0100")

Óscar Fuentes <ofv@wanadoo.es> writes:

> With a fresh MSYS2/Mingw-w64 build executed on Windows 11 64bits with
> -Q, emacs mangles the output of processes and does not detect when they
> end.
>
> For instance, with emacs -Q
>
> M-x shell
>
> it shows
>
> icrosoft Windows [Version <omitted rest of output>
>
> Note the missing initial M. Then, emacs hangs (no input possible, C-g
> doen't work) showing (Shell:run) on the modeline.

With my Emacs 30 (d0766c0999) build, started from cmd.exe with
'runemacs -Q' and M-x shell RET, I get:

--8<---------------cut here---------------start------------->8---
Microsoft Windows [Version 10.0.19045.4046]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

z:dir\>gcc -v
gcc -v
Using built-in specs.
...
--8<---------------cut here---------------end--------------->8---

With 'emacs -Q' started from a MinGW64 shell, M-x shell RET says:

--8<---------------cut here---------------start------------->8---
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

$ gcc -v
Using built-in specs.
...
--8<---------------cut here---------------end--------------->8---

Both versions work, despite the bash message.  I didn't try eshell.

Best, Arash



  parent reply	other threads:[~2024-03-02 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 16:46 (Windows) Problems with processes on master branch Óscar Fuentes
2024-03-01 16:52 ` Eli Zaretskii
2024-03-01 17:12   ` Óscar Fuentes
2024-03-01 18:10     ` Corwin Brust
2024-03-02 12:16 ` Arash Esbati [this message]
2024-03-02 23:17   ` Óscar Fuentes

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=867cikakxh.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ofv@wanadoo.es \
    /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.
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).