unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yasuhiro Kimura <yasu@utahime.org>
Cc: 55386@debbugs.gnu.org
Subject: bug#55386: 29.0.50; check-declare-directory doesn't work on Windows
Date: Thu, 12 May 2022 17:57:01 +0200	[thread overview]
Message-ID: <878rr6ycaa.fsf@gnus.org> (raw)
In-Reply-To: <20220513.002244.1042559713148422728.yasu@utahime.org> (Yasuhiro Kimura's message of "Fri, 13 May 2022 00:22:44 +0900 (JST)")

Yasuhiro Kimura <yasu@utahime.org> writes:

> [How to reproduce the problem]
>
> 1. cd C:/Users/yasu/Temp
> 2. git clone https://git.savannah.gnu.org/git/emacs.git
> 3. Start Emacs with 'emacs -Q'
> 4. Type '(check-declare-directory "C:/Users/yasu/Temp/emacs/lisp")'
>    and C-j.

[...]

> Debugger entered--Lisp error: (file-error "Opening input file" "Invalid argument" "c:/Users/yasu/ファイルが見つかりません - \"^[ \11]*(declare-funct...")
>   insert-file-contents("ファイルが見つかりません - \"^[ \11]*(declare-function\"")
>   check-declare-scan("ファイルが見つかりません - \"^[ \11]*(declare-function\"")
>   check-declare-files("ファイルが見つかりません - \"^[ \11]*(declare-function\"")
>   apply(check-declare-files "ファイルが見つかりません - \"^[ \11]*(declare-function\"")

check-declare-directory is just a wrapper around `find', and I'm surprised
that this even vaguely works on Windows:

(defun check-declare-directory (root)
[...]
  (let ((files (process-lines-ignore-status
                find-program root
                "-name" "*.el"
                "-exec" grep-program
                "-l" "^[ \t]*(declare-function" "{}" "+")))

If you run this "manually", what does it output?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-12 15:57 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 [this message]
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
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=878rr6ycaa.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55386@debbugs.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).