From: Dmitry Gutov <dgutov@yandex.ru>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 44297@debbugs.gnu.org, leungbk@mailfence.com,
Juri Linkov <juri@linkov.net>
Subject: bug#44297: [Feature request] project.el: Additional utility functions
Date: Fri, 30 Oct 2020 19:40:23 +0200 [thread overview]
Message-ID: <6bef1bb9-5f33-030e-2cf5-583c1a79dda5@yandex.ru> (raw)
In-Reply-To: <87wnz8io18.fsf@tcd.ie>
On 30.10.2020 01:57, Basil L. Contovounesios wrote:
>> What I don't understand, is why should it be in the project- namespace? Looking
>> for a file with the same name in the current dir doesn't execute the notion of
>> the current project, even a little bit.
>>
>> Projectile does a project-wide search for a file with the same basename (but a
>> different extension). Is that actually useful?
>
> Maybe when e.g. headers and source files are in different directories?
All right then.
> I don't know whether that's already supported by find-file.el.
Apparently it's done using the ff-search-directories variable.
I'm not sure about usefulness of this, given the default value lists
system directories. Was the user always supposed to customize it to list
the source dirs in the current project?
next prev parent reply other threads:[~2020-10-30 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 2:52 bug#44297: [Feature request] project.el: Additional utility functions Brian Leung via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-29 9:03 ` Juri Linkov
2020-10-29 23:20 ` Dmitry Gutov
2020-10-29 23:57 ` Basil L. Contovounesios
2020-10-30 0:47 ` Brian Leung via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30 17:47 ` Dmitry Gutov
2020-10-30 17:40 ` Dmitry Gutov [this message]
2020-10-30 7:23 ` Juri Linkov
2020-10-30 17:42 ` Dmitry Gutov
2020-10-31 19:18 ` Juri Linkov
2020-11-02 0:28 ` Dmitry Gutov
2020-10-29 23:31 ` 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=6bef1bb9-5f33-030e-2cf5-583c1a79dda5@yandex.ru \
--to=dgutov@yandex.ru \
--cc=44297@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=juri@linkov.net \
--cc=leungbk@mailfence.com \
/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.