From: Manuel Uberti <manuel.uberti@inventati.org>
To: Dmitry Gutov <dgutov@yandex.ru>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: project-find-file: switch to include non-tracked files
Date: Fri, 15 Oct 2021 15:05:15 +0200 [thread overview]
Message-ID: <0d5bdd80-4a3c-d038-714f-91d7dad019f5@inventati.org> (raw)
In-Reply-To: <3abfb5f5-a034-d234-fe6a-de00e01782b9@yandex.ru>
On 15/10/21 14:12, Dmitry Gutov wrote:
> Both of these are for the default project-files behavior.
>
> How would we leverage them?
Not sure, sorry. I don't know the rationale behind the decision to stop using
vc-directory-exclusion-list, and I have to dig deeper in project.el to better
understand what project-ignores and a project-vc-ignores do and how they are
used at the moment.
> Thanks for checking, I've pushed the patch (slightly tweaked).
I'll give it a try later and come back if I find any issue with it.
> Perhaps ideally, we'd just ignore such directories, leaving it to the user to
> figure out why the files are not showing up. But 'find' doesn't make it easy.
> First, adding
>
> -o -type d -a ! -readable
>
> kinda works, but it's a GNU extension, not available on e.g, macOS, so it's a
> no-go. And even with the '-type d' qualifier it adds some runtime cost, somehow.
>
> I suppose we could just redirect stderr to null (like vc-git--out-ok does) and
> check for success by the presence of \0 chars in the output, but that's both
> quite lax and leaves us unable to print the error message when indeed some other
> kind of error happens. I guess redirecting stderr to a file is the remaining
> option...
I am ok with customizing a setting to ignore specific directories, but as you
said before it should not slow down find. But parsing \0 chars sound a bit scary
to me, so yeah, it's a tricky one.
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2021-10-15 13:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 8:33 project-find-file: switch to include non-tracked files Manuel Uberti
2021-10-04 11:24 ` Philip Kaludercic
2021-10-04 13:44 ` Stefan Kangas
2021-10-04 13:50 ` Manuel Uberti
2021-10-04 14:06 ` Stefan Kangas
2021-10-05 19:28 ` Dmitry Gutov
2021-10-05 19:47 ` Dmitry Gutov
2021-10-06 5:18 ` Manuel Uberti
2021-10-06 6:05 ` Dmitry Gutov
2021-10-06 6:12 ` Manuel Uberti
2021-10-14 0:47 ` Dmitry Gutov
2021-10-14 6:37 ` Manuel Uberti
2021-10-14 12:01 ` Dmitry Gutov
2021-10-14 12:06 ` Manuel Uberti
2021-10-14 21:55 ` Dmitry Gutov
2021-10-15 5:24 ` Manuel Uberti
2021-10-15 12:12 ` Dmitry Gutov
2021-10-15 13:05 ` Manuel Uberti [this message]
2021-10-15 13:25 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2021-05-04 13:39 Manuel Uberti
2021-05-04 14:04 ` Stefan Kangas
2021-05-04 14:16 ` Dmitry Gutov
2021-05-04 14:55 ` Manuel Uberti
2021-05-04 16:43 ` Dmitry Gutov
2021-05-04 16:57 ` Manuel Uberti
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=0d5bdd80-4a3c-d038-714f-91d7dad019f5@inventati.org \
--to=manuel.uberti@inventati.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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 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).