From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.synacek@posteo.org, 55632-done@debbugs.gnu.org
Subject: bug#55632: [PATCH] Add new user option project-vc-find-tracked-only
Date: Sat, 4 Jun 2022 03:37:21 +0300 [thread overview]
Message-ID: <ed43d7f9-00ea-7528-4e53-9e0383742f5a@yandex.ru> (raw)
In-Reply-To: <83a6aue1y2.fsf@gnu.org>
Version: 29.1
On 03.06.2022 08:44, Eli Zaretskii wrote:
>> Date: Fri, 3 Jun 2022 02:45:19 +0300
>> Cc: 55632@debbugs.gnu.org, raaahh@gmail.com
>> From: Dmitry Gutov <dgutov@yandex.ru>
>>
>> On 02.06.2022 22:19, Eli Zaretskii wrote:
>>> Can we please tell more about what does "include untracked files"
>>> mean? Include where and in what sense?
>>
>> Has them considered to be part of the project. Which in practice means
>> including them in a project's list of files. For the purposes for
>> project-find-file, project-find-regexp, and all other commands that
>> build on top of 'project-files'.
>>
>> How would you phrase that better?
>
> Something like this:
>
> If non-nil, files untracked by a VCS are considered to be part of
> the project by a VC project based on that VCS.
A bit unwieldy IMHO, but I don't mind. As long as you only objected to
the NEWS entry.
The addition to the manual, which is also usually considered user-level
text, only continues the style of the preceding sentence. And the
docstring has to be precise either way.
>>> Bonus points for explaining
>>> this without ever alluding to "backend", as that is not necessarily a
>>> user-level concept in this case.
>>
>> The variable only affects a particular backend. It's only meaningful
>> when there is a VCS anyway.
>
> I understand. My point was to avoid using the word "backend" in
> user-level documentation, as much as possible.
>
>>> Also, is it "VC project backend" or "Project's VC backend"?
>>
>> I would say both mean the same thing, but the latter seems to be more
>> unambiguous.
>
> Well, if you are okay with my alternative wording above, it solves
> this problem as well.
Amended and pushed, thank you both.
next prev parent reply other threads:[~2022-06-04 0:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 9:08 bug#55632: [PATCH] Add new user option project-vc-find-tracked-only Jan Synáček
2022-05-27 11:01 ` Lars Ingebrigtsen
2022-05-27 13:55 ` Dmitry Gutov
2022-05-29 21:41 ` Dmitry Gutov
2022-05-30 11:00 ` jan.synacek
2022-05-31 22:49 ` Dmitry Gutov
2022-06-02 19:01 ` jan.synacek
2022-06-02 19:19 ` Eli Zaretskii
2022-06-02 23:45 ` Dmitry Gutov
2022-06-03 5:44 ` Eli Zaretskii
2022-06-04 0:37 ` Dmitry Gutov [this message]
2022-06-04 6:29 ` Eli Zaretskii
2022-06-04 9:40 ` Dmitry Gutov
2022-05-30 10:08 ` jan.synacek
2022-05-31 22:57 ` Dmitry Gutov
2022-06-01 15:21 ` jan.synacek
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=ed43d7f9-00ea-7528-4e53-9e0383742f5a@yandex.ru \
--to=dgutov@yandex.ru \
--cc=55632-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jan.synacek@posteo.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.