unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: yasu@utahime.org, 55386@debbugs.gnu.org
Subject: bug#55386: 29.0.50; check-declare-directory doesn't work on Windows
Date: Fri, 13 May 2022 15:35:37 +0300	[thread overview]
Message-ID: <83pmkhmwyv.fsf@gnu.org> (raw)
In-Reply-To: <878rr5wrma.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  13 May 2022 14:21:01 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: yasu@utahime.org,  55386@debbugs.gnu.org
> Date: Fri, 13 May 2022 14:21:01 +0200
> 
> > Why are you surprised?
> 
> Because:
> 
> > So I suspect the OP doesn't have a port of GNU Find
> > on Path before the Windows program of the same name (which does
> > something completely different), or maybe the version of Find or Grep
> > the OP has don't support non-ASCII characters encoded in the OP's
> > locale's codepage.
> 
> There's always stuff like this in Windows-related bug reports.  😀

There's a difference between expecting problems and being surprised it
can work at all.

> > I wonder whether it could be a good idea to replace the find/grep
> > command by something that traverses the files in Lisp, like
> > dired-do-search or somesuch?  This would resolve any problems with
> > file names and incompatible versions of Find and Grep.
> 
> It would be massively slower, though.

I'm not sure.  How much time does it take for the find/grep command to
finish working on our lisp/ directory on your system?

And this command is not really time-critical anyway.

In any case, we could use the Lisp path only on Windows, since having
a slower command is better than having a broken command.





  reply	other threads:[~2022-05-13 12:35 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 [this message]
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=83pmkhmwyv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55386@debbugs.gnu.org \
    --cc=larsi@gnus.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).