From: vincent.belaiche@gmail.com (Vincent Belaïche)
To: 27393@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Cc: "Vincent Belaïche" <vincent.belaiche@gmail.com>
Subject: bug#27393: 25.2.50; *Find* file visiting does not work well for me.
Date: Fri, 16 Jun 2017 19:15:32 +0200 [thread overview]
Message-ID: <84o9tndfbf.fsf@gmail.com> (raw)
In-Reply-To: <84wp8ccjtg.fsf@gmail.com>
Le 16/06/2017 à 15:10, Eli Zaretskii a écrit :
> Why are you using MSYS programs with a native Windows build of Emacs?
> Why not use a native port of GNU Find instead?
Just to be fully complete about this one, the silly reason was that:
1) MSYS/find was already installed on my machine.
2) MSYS/find was supposedly good enough because command find-name-dired
only outputs relative paths.
3) I was not aware of MSYS/Find bug
(https://sourceforge.net/p/mingw/bugs/2161/) --- or maybe I had
forgotten about it, I have the impression that I had already met some
similar issue quite some ago.
Now:
1) You are fully right, using EZWinPorts
https://sourceforge.net/projects/ezwinports/files/findutils-4.2.30-5-w64-bin.zip/download
does the job very well. In the end this is what I am doing now.
2) The other work around (which you may not like) is tampering the
find-ls-option variable to set its car to "-exec ls -dils {} +" and
continue with the MSYS find. I have tried that and it also fixes it,
however I preferred to use EZWinPorts because the findutil is more
recent and that allowed me to take the win64 port.
Vincent.
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
prev parent reply other threads:[~2017-06-16 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:23 bug#27393: 25.2.50; *Find* file visiting does not work well for me Vincent Belaïche
2017-06-16 10:46 ` Vincent Belaïche
2017-06-16 13:10 ` Eli Zaretskii
2017-06-16 14:12 ` Vincent Belaïche
2017-06-16 17:15 ` Vincent Belaïche [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84o9tndfbf.fsf@gmail.com \
--to=vincent.belaiche@gmail.com \
--cc=27393@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.