From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 49283@debbugs.gnu.org
Subject: bug#49283: [PATCH] 27.2; `(call-process "program" null-device ...)' fails over TRAMP from local MS Windows
Date: Wed, 30 Jun 2021 09:24:47 +0200 [thread overview]
Message-ID: <87a6n7zuf4.fsf@gmx.de> (raw)
In-Reply-To: <CANh=_JGCOs_1uhT_zgTUBZ5+4DezZh8beU8nWpZo+Tahui3qzQ@mail.gmail.com> (Jim Porter's message of "Tue, 29 Jun 2021 22:14:19 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> I noticed an issue when trying to use flyspell (or ispell) using
> hunspell from a local MS Windows system on a TRAMP file. It results in
> an error that it can't find the file "/sshx:server:/path/to/NUL". I
> narrowed this down to the fact that
> `ispell-find-hunspell-dictionaries' calls `call-process' with `infile'
> set to `null-device'.
`call-process' doesn't know of remote files. You must use `process-file' instead.
> To see this in action:
>
> emacs -Q
> C-x C-f /sshx:server:~/path/to/file.txt
> M-: (setq ispell-program-name "hunspell") RET
> M-x flyspell-mode
> ;; or...
> M-: (call-process "something" null-device) RET
It is not a good idea to use `null-device' as INFILE, just use nil. At
least in the `process-file' case, Tramp shall know which value to take
for `null-device'.
After all, it seems to be rather a flyspell/ispell feature request to
support remote files.
Best regards, Michael.
next prev parent reply other threads:[~2021-06-30 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 5:14 bug#49283: [PATCH] 27.2; `(call-process "program" null-device ...)' fails over TRAMP from local MS Windows Jim Porter
2021-06-30 7:24 ` Michael Albinus [this message]
2021-06-30 17:16 ` Jim Porter
2021-07-01 11:07 ` Lars Ingebrigtsen
2021-07-01 12:26 ` Michael Albinus
2021-07-01 12:34 ` Lars Ingebrigtsen
2021-07-01 13:12 ` Eli Zaretskii
2021-07-01 19:45 ` Jim Porter
2021-07-02 6:37 ` Eli Zaretskii
2021-07-02 18:47 ` Jim Porter
2021-07-03 7:02 ` Eli Zaretskii
2021-07-04 13:32 ` 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=87a6n7zuf4.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=49283@debbugs.gnu.org \
--cc=jporterbugs@gmail.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).