From: Theodor Thornhill <theo@thornhill.no>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 41736@debbugs.gnu.org
Subject: bug#41736: 28.0.50; project.el - support global patterns for project-ignores
Date: Sat, 06 Jun 2020 10:10:59 +0000 [thread overview]
Message-ID: <MSGsnuVt81aMMDb_fvCTKjzU_YmG66YePxPPLbMqtevBwZsAizm7dLvlWSOKjGCxbA1NcljwCnT95BBX8T_zlHoXJLQ7xcEkMIZLNmrKYHw=@thornhill.no> (raw)
In-Reply-To: <87y2p0cyfh.fsf@tcd.ie>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Sat, Jun 6, 2020 at 11:53, Basil L. Contovounesios <contovob@tcd.ie> wrote:
> Note that defcustoms are generally a user-level preference and should
> therefore generally not be modified by major modes or other Lisp.
> Yeah, absolutely. Unclear wording from my end.
What I mean is:
We seem to want the vc backend no matter what. However - if I open dired in root and execute “project-find-files” all the stuff I want ignored is not. I get the fast backend, but may search a million obfuscated minified files.
I think what I want is to be able to say:
1. Use the vc backed “major-mode” project
2. Use the vc backed “major-modes” project
Not sure how this would be implemented most clearly, but maybe the “project-vc-ignores” defcustom in init.el is the magic wand here?
If so - this bug report could be reduced to “add documentation to clarify this” :)
Theo
[-- Attachment #2: Type: text/html, Size: 1351 bytes --]
next prev parent reply other threads:[~2020-06-06 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 9:45 bug#41736: 28.0.50; project.el - support global patterns for project-ignores Theodor Thornhill
2020-06-06 9:53 ` Basil L. Contovounesios
2020-06-06 10:10 ` Theodor Thornhill [this message]
2020-06-06 11:08 ` Dmitry Gutov
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='MSGsnuVt81aMMDb_fvCTKjzU_YmG66YePxPPLbMqtevBwZsAizm7dLvlWSOKjGCxbA1NcljwCnT95BBX8T_zlHoXJLQ7xcEkMIZLNmrKYHw=@thornhill.no' \
--to=theo@thornhill.no \
--cc=41736@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/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.