From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-27 561e9fb: Improve documentation of project.el commands
Date: Mon, 23 Mar 2020 16:29:11 +0200 [thread overview]
Message-ID: <83o8snb0w8.fsf@gnu.org> (raw)
In-Reply-To: <1e1dbc65-f232-dcdf-969b-a34cb3276914@yandex.ru> (message from Dmitry Gutov on Sun, 22 Mar 2020 23:24:13 +0200)
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 22 Mar 2020 23:24:13 +0200
>
> > Yes, I was aware of that. But since saying that a project is a
> > collection of arbitrary files would make the issue harder to
> > understand,
>
> Regardless of how we define a project, this heading can say "Commands
> for handling files in a project" without a loss of clarify, I believe.
It isn't about clarity, I think, it's about making the feature less
abstract and more lucrative to our audience.
> > I decided to compromise, as I believe currently no one
> > really uses this for non-program files. If this ever becomes a
> > practical problem, we can always rephrase.
>
> You're probably responding to my second quote here. But why not say
> "Command for handling files in a project"? Again, no real loss of
> clarity, this sentence is not a definition.
For the same reason: to be more attractive to the reader.
> >> And is "hierarchy of directories" a better term than "directory tree"?
> >
> > I think it's the same thing. Wed use both interchangeably in our
> > documentation. Why, you think "directory tree" will be easier to
> > understand or something?
>
> This choice of words gives me a somewhat more complicated mental image,
> like a sparse collection of subdirectories, where some are included, and
> some are not. Which kind of comes out to the same thing, but in a more
> complex way.
That's not what I had in mind, but these commands do support sparse
trees as well: it's all about what are "the project files", isn't it?
Would "directory tree hierarchy" solve your problems here?
next prev parent reply other threads:[~2020-03-23 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200321112658.6254.3414@vcs0.savannah.gnu.org>
[not found] ` <20200321112700.1883720E43@vcs0.savannah.gnu.org>
2020-03-21 21:19 ` emacs-27 561e9fb: Improve documentation of project.el commands Dmitry Gutov
2020-03-22 14:18 ` Eli Zaretskii
2020-03-22 21:24 ` Dmitry Gutov
2020-03-23 14:29 ` Eli Zaretskii [this message]
2020-03-23 16:40 ` Dmitry Gutov
2020-03-23 16:50 ` Eli Zaretskii
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=83o8snb0w8.fsf@gnu.org \
--to=eliz@gnu.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 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.