unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: "Process shell finished" on Windows
Date: Sat, 14 Jan 2023 13:31:47 +0200	[thread overview]
Message-ID: <83y1q573oc.fsf@gnu.org> (raw)
In-Reply-To: <ecd0dvilhaawfp.fsf@boyer.boyerenterprises.org> (message from Galen Boyer on Fri, 13 Jan 2023 17:42:18 -0500)

> From: Galen Boyer <galendboyer@gmail.com>
> Date: Fri, 13 Jan 2023 17:42:18 -0500
> 
> Galen Boyer <galendboyer@gmail.com> writes:
> 
> In comint.el, line #1914 we see the following code.
> 
>         (set-marker comint-accum-marker nil)
>         (let ((comint-input-sender-no-newline no-newline))
>           (funcall comint-input-sender proc input).)
> 
> When the command prompt first displayed "Process shell finished"
> the cursor was at the `.' above.

Sounds like a bug, but I don't see it here, so it's a bit hard to
investigate.

When you are at that place in the execution, and you see "Process
shell finished", please produce a Lisp backtrace and post it here.  (I
assume you are stepping through the code with Edebug, in which case
typing 'd' will produce the backtrace.)

What are the commands with which you see this issue?  Are they .exe
executables, are they some kinds of shell scripts or batch files, are
they something else?  If they are all executables, where did you get
them?  You only posted a single example of a command which causes
this, and you mentioned Cygwin, but you never described any additional
details.



  reply	other threads:[~2023-01-14 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 18:42 "Process shell finished" on Windows Galen Boyer
2023-01-13 14:49 ` Galen Boyer
2023-01-13 15:10   ` Eli Zaretskii
2023-01-13 22:04     ` Galen Boyer
2023-01-13 22:42       ` Galen Boyer
2023-01-14 11:31         ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-22 17:16 Galen Boyer
2022-12-23  7:05 ` 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=83y1q573oc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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).