unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Sharman <rsharman@pobox.com>
Cc: 45951@debbugs.gnu.org
Subject: bug#45951: 27.1; comint-redirect-results-list-from-process sometimes fails to skip over command if echoed
Date: Tue, 19 Jan 2021 07:12:08 +0100	[thread overview]
Message-ID: <87eeiho3pj.fsf@gnus.org> (raw)
In-Reply-To: <2E84331E-C133-4324-9C76-B3CEB0904319@pobox.com> (Richard Sharman's message of "Mon, 18 Jan 2021 21:07:54 -0800")

(Please keep the debbugs address in the CC header -- otherwise the bug
tracker won't receive the message.  Resent to put it into the tracker.)

Richard Sharman <rsharman@pobox.com> writes:

>> On Jan 18, 2021, at 8:03 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> 
>> Richard Sharman <rsharman@pobox.com> writes:
>> 
>>> The latter problem can be fixed by calling comint-carriage-motion before
>>> the test is done; the former by looking-at (regexp-quote command)
>>> instead of just at command.
>> 
>> This bit seems to have been fixed in Emacs 28.
>
> Ok, thanks.
>
>> On Jan 18, 2021, at 8:24 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> 
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> 
>>> comint-redirect-send-command-to-process: No prompt found or
>>> ‘comint-prompt-regexp’ not set properly
>>> 
>>> Do you have a recipe, starting from "emacs -Q"?
>> 
>> Oh, we have to `M-x shell' manually first, and then we don't get that
>> error.
>> 
>
> Yes, I think that’s another bug I was going to look into but didn’t.
> After the M-x shell it works.
>
>> But the `M-x example' just infloops for me -- this bit never completes:
>> 
>>      (while (and (null comint-redirect-completed)
>> 		  (accept-process-output process)))
>> 
>
> I saw that once but couldn’t reproduce it. I *think* it happened when
> there was a comint process that had terminated (abnormally perhaps?) I
> tried to see why accept-process-output didn’t return but it was in
> C-code and I didn’t feel up to chasing it.  I think I manually deleted
> the process but I may have restarted emacs; after that I didn’t see it
> happen again.
> …
> I tried running example.el just now from an emacs -Q and apart from
> the “no prompt found” it works fine; I haven’t been able to reproduce
> the problem of accept-process-output not returning.
>
> Richard





  parent reply	other threads:[~2021-01-19  6:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  2:51 bug#45951: 27.1; comint-redirect-results-list-from-process sometimes fails to skip over command if echoed Richard Sharman
2021-01-19  4:03 ` Lars Ingebrigtsen
2021-01-19  4:24   ` Lars Ingebrigtsen
     [not found]   ` <2E84331E-C133-4324-9C76-B3CEB0904319@pobox.com>
2021-01-19  6:12     ` Lars Ingebrigtsen [this message]
2021-07-30 12:29       ` Lars Ingebrigtsen

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=87eeiho3pj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45951@debbugs.gnu.org \
    --cc=rsharman@pobox.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).