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: Tue, 4 May 2021 16:55:12 +0200 [thread overview]
Message-ID: <28f1e636-0b95-fa03-5d3a-78c27d24ee48@inventati.org> (raw)
In-Reply-To: <9d620142-6009-d1bf-813f-17d091511c58@yandex.ru>
On 04/05/21 16:16, Dmitry Gutov wrote:
> The current behavior is to include the untracked files (unless they are in
> .gitignore). And you can specify additional ignores through the
> project-vc-ignores variable.
>
> If that is not enough, please outline your usage scenario(s).
Sure, I'll try to explain myself better. I have Git-versioned projects where I
usually track an .envrc.sample file for everyone to use as a starting point on
their own machines. Developers are instructed to copy that file to a local
(i.e., untracked) .envrc file. Since there could (and usually will) be
information we don't want to be tracked on Git (e.g., one's own system-related
customizations), .envrc is listed in .gitignore.
Every now and then, I need to open that .envrc file and add something, but
because it is listed in .gitignore, the file doesn't show up in project-find-file.
What helm-ls-git offers is the possibility to hit C-c i and showing the
untracked files. This doesn't involve changing any setting, it's just a matter
of pressing C-c i whenever is needed. This is useful because generally I want
everything listed in .gitignore to be ignored by project-find-file, but there
are small exceptions such as this where I want to edit an ignored file without
using find-file to get to it.
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2021-05-04 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 13:39 project-find-file: switch to include non-tracked files Manuel Uberti
2021-05-04 14:04 ` Stefan Kangas
2021-05-04 14:16 ` Dmitry Gutov
2021-05-04 14:55 ` Manuel Uberti [this message]
2021-05-04 16:43 ` Dmitry Gutov
2021-05-04 16:57 ` Manuel Uberti
-- strict thread matches above, loose matches on Subject: below --
2021-10-04 8:33 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
2021-10-15 13:25 ` 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
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=28f1e636-0b95-fa03-5d3a-78c27d24ee48@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).