From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yasuhiro Kimura <yasu@utahime.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 55386@debbugs.gnu.org
Subject: bug#55386: 29.0.50; check-declare-directory doesn't work on Windows
Date: Fri, 13 May 2022 14:25:10 +0200 [thread overview]
Message-ID: <874k1twrfd.fsf@gnus.org> (raw)
In-Reply-To: <20220513.023530.164806185269303998.yasu@utahime.org> (Yasuhiro Kimura's message of "Fri, 13 May 2022 02:35:30 +0900 (JST)")
Yasuhiro Kimura <yasu@utahime.org> writes:
> insert-file-contents("/usr/bin/find: paths must precede expression: `with-editor.el'")
> check-declare-scan("/usr/bin/find: paths must precede expression: `with-editor.el'")
> check-declare-files("/usr/bin/find: paths must precede expression: `with-editor.el'" "/usr/bin/find: possible unquoted pattern after predicate `-name'?")
> apply(check-declare-files ("/usr/bin/find: paths must precede expression: `with-editor.el'" "/usr/bin/find: possible unquoted pattern after predicate `-name'?"))
> check-declare-directory("~/Work/Emacs/with-editor/lisp/")
[...]
> But when I directly evaluated check-declare-directory from *scratch*
> buffer, I executed emacs from command prompt of Windows. And in this
> case there is neither find.exe nor grep.exe in my PATH directories. So
> check-declare-directory fails differently. And I wrongly reported it
> as the bug of Emacs. Actually if I execute emacs from shell of MSYS2,
> then steps of original bug report mail results in expected behavior.
>
> I don't know why above build error happens. But probably it is bug of
> the elisp applications in question. So I'll report it to the author
> of them.
There does seem to be an issue in `check-declare-directory' in Emacs
under Windows, though -- find is complaining about syntax errors in the
"find" command we're constructing.
Eli, does `check-declare-directory' work for you on some Lisp directory
on Windows?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-13 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 15:22 bug#55386: 29.0.50; check-declare-directory doesn't work on Windows Yasuhiro Kimura
2022-05-12 15:57 ` Lars Ingebrigtsen
2022-05-12 16:43 ` Eli Zaretskii
2022-05-13 12:21 ` Lars Ingebrigtsen
2022-05-13 12:35 ` Eli Zaretskii
2022-05-13 15:46 ` Lars Ingebrigtsen
2022-05-14 9:09 ` Eli Zaretskii
2022-05-14 11:40 ` Lars Ingebrigtsen
2022-05-14 12:05 ` Eli Zaretskii
2022-05-14 15:36 ` Lars Ingebrigtsen
2022-05-14 16:09 ` Eli Zaretskii
2022-05-14 13:27 ` Eli Zaretskii
2022-05-14 13:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 13:44 ` Eli Zaretskii
2022-05-14 15:37 ` Lars Ingebrigtsen
2022-05-14 16:34 ` Eli Zaretskii
2022-05-12 17:35 ` Yasuhiro Kimura
2022-05-13 12:25 ` Lars Ingebrigtsen [this message]
2022-05-13 12:31 ` 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=874k1twrfd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55386@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yasu@utahime.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).