From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56865@debbugs.gnu.org
Subject: bug#56865: M-x find-dired fails with "Wrong type: processp, nil"
Date: Tue, 2 Aug 2022 13:24:25 +0200 [thread overview]
Message-ID: <CAG7BpaoSRMQQ3-ifyhLi0hq5PjE1qdyq7cqGY9Wt-_O-v+PTxQ@mail.gmail.com> (raw)
In-Reply-To: <87pmhjylv1.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Seems so. I guess with the way Elisp works it is even correct, because (as
I understand) Elisp has no way to notice that process has died if there are
no IO calls between `shell-process' and `set-process-*'. But it does feel
dirty. (Also that `(sit-for 1)' a few lines above feels dirty.)
Paul
On Tue, 2 Aug 2022 at 12:35, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Paul Pogonyshev <pogonyshev@gmail.com> writes:
>
> > Tested also with `emacs -Q', so this is not a problem of my
> configuration.
> >
> > 1. Open (a slow) remote connection, with TRAMP
> > 2. Run M-x find-dired RET, arguments not important
> > 3. Internal error "Wrong type: processp, nil" appears
> >
> > Debugging suggests that it happens in `find-dired-with-command' when
> calling
> > `set-process-filter'. Apparently the asynchronously started shell
> command started ~
> > 30 lines above counts as having finished (?) by then.
>
> The proper fix here would be to have a way to specify the
> filter/sentinel in `shell-command', since that's the only way to really
> guarantee that we'll be getting the output here.
>
> But some testing seems to indicate that just moving the settings up
> until right after the `shell-command' makes things work, so I've now
> made that trivial fix in Emacs 29. Does this fix this issue for you,
> too?
>
>
>
[-- Attachment #2: Type: text/html, Size: 1827 bytes --]
next prev parent reply other threads:[~2022-08-02 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 8:06 bug#56865: M-x find-dired fails with "Wrong type: processp, nil" Paul Pogonyshev
2022-08-02 10:34 ` Lars Ingebrigtsen
2022-08-02 11:24 ` Paul Pogonyshev [this message]
2022-08-02 11:28 ` Lars Ingebrigtsen
2022-08-10 13:26 ` Paul Pogonyshev
2022-08-12 15:04 ` Lars Ingebrigtsen
2022-08-12 15:33 ` Michael Albinus
2022-08-13 11:43 ` Lars Ingebrigtsen
2022-12-01 7:33 ` Liu Hui
2022-12-01 9:21 ` Michael Albinus
2022-12-03 13:38 ` Paul Pogonyshev
2023-09-06 22:41 ` Stefan Kangas
2022-08-12 15:12 ` Paul Pogonyshev
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=CAG7BpaoSRMQQ3-ifyhLi0hq5PjE1qdyq7cqGY9Wt-_O-v+PTxQ@mail.gmail.com \
--to=pogonyshev@gmail.com \
--cc=56865@debbugs.gnu.org \
--cc=larsi@gnus.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.
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).