From: Galen Boyer <galendboyer@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: "Process shell finished" on Windows
Date: Fri, 13 Jan 2023 17:42:18 -0500 [thread overview]
Message-ID: <ecd0dvilhaawfp.fsf@boyer.boyerenterprises.org> (raw)
In-Reply-To: ecd0dvmt6may7j.fsf@boyer.boyerenterprises.org
Galen Boyer <galendboyer@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Galen Boyer <galendboyer@gmail.com>
>>> Date: Fri, 13 Jan 2023 09:49:07 -0500
>>>
>>> Just hoping someone might be able to give me some pointers on where to
>>> turn to debug this?
>>
>> I would start by looking in the Windows Event Log, under Applications.
>> It sounds like the shell dies for some reason, and the Windows Event
>> Log could have some hint about the reason(s).
>
> I'm already seeing very helpful information.
>
> Thank you so much!
Not done, but decided I would try to get some information from edebug.
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.
I'm not sure how useful the above might be but maybe long-term Elisp
folks as yourself might be able to let me know if digging further this
route might be helpful?
--
Galen Boyer
next prev parent reply other threads:[~2023-01-13 22:42 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 [this message]
2023-01-14 11:31 ` Eli Zaretskii
-- 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=ecd0dvilhaawfp.fsf@boyer.boyerenterprises.org \
--to=galendboyer@gmail.com \
--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).