unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 44297@debbugs.gnu.org
Cc: leungbk@mailfence.com
Subject: bug#44297: [Feature request] project.el: Additional utility functions
Date: Thu, 29 Oct 2020 11:03:27 +0200	[thread overview]
Message-ID: <871rhhv4q8.fsf@mail.linkov.net> (raw)
In-Reply-To: <1785587458.69035.1603939939547@ichabod.co-bxl> (Brian Leung via's message of "Thu, 29 Oct 2020 03:52:19 +0100 (CET)")

> 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).

Another question: how it should work?  Maybe running this command
should completing-read on all files with the same basename
ignoring the extension?

> project-find-file-in-directory: completing-read for a directory within
> the project, and then within the selected directory, completing-read
> for a file within that directory
> project-find-directory: completing-read for a directory within the project

Another useful command would be:
project-find-file-only using completing-read to match on file names only,
not on directory parts.

> project-recentf: completing-read recently-accessed files in the project

All project file-reading commands could provide a list of recent files
as the default values available via M-n key presses.

> project-gdb: GDB in project root directory





  reply	other threads:[~2020-10-29  9:03 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 [this message]
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
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=871rhhv4q8.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=44297@debbugs.gnu.org \
    --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).