From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 44297@debbugs.gnu.org, leungbk@mailfence.com,
Juri Linkov <juri@linkov.net>
Subject: bug#44297: [Feature request] project.el: Additional utility functions
Date: Thu, 29 Oct 2020 23:57:07 +0000 [thread overview]
Message-ID: <87wnz8io18.fsf@tcd.ie> (raw)
In-Reply-To: <64182b62-dad4-08db-379b-acfddea26327@yandex.ru> (Dmitry Gutov's message of "Fri, 30 Oct 2020 01:20:21 +0200")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 29.10.2020 11:03, Juri Linkov wrote:
>>> It would be nice if project.el had the following interactive functions:
>>>
>>> project-find-other-file: Find a file with the same basename as the current file but a different extension
>> Maybe then it should be named project-find-other-extension?
>> Otherwise, project-find-other-file might imply a similarity
>> with find-alternate-file (C-x C-v).
>
> I think the term is pretty much established:
> https://www.emacswiki.org/emacs/FindOtherFile
>
> Projectile also has a command with a similar name.
>
> The feature will be pretty C/C++-centric
Not if it's customised via ff-other-file-alist or similar.
> , but I suppose it's useful enough.
> 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?
I don't know whether that's already supported by find-file.el.
--
Basil
next prev parent reply other threads:[~2020-10-29 23:57 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 [this message]
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
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
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=87wnz8io18.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=44297@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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 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).