From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 55267@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#55267: 29.0.50; Provide customization to save project-find-file arg to savehist
Date: Mon, 30 May 2022 11:38:40 +0530 [thread overview]
Message-ID: <87ilpnh7rr.fsf@codeisgreat.org> (raw)
In-Reply-To: <51efc8c0-78f8-07ba-7a56-107331956fce@yandex.ru> (Dmitry Gutov's message of "Mon, 30 May 2022 00:44:19 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 12.05.2022 19:38, Juri Linkov wrote:
>> BTW, here is another improvement for project-find-file.
>> If there is no file name under point, it could propose
>> the current file name for editing in the minibuffer,
>> to find another file based on the current file
>> when their names are similar.
>
> Here as well: if you find this helpful, that sounds okay to me.
>
> I haven't ever felt a need for this particular behavior, but it
> shouldn't hurt either.
To be consistent with other subsystems of Emacs, we can do something
that Dired does.
1. Press ’R’ to rename a file.
2. Then press ’M-n’. It invokes (next-history-element) which fills
current file in the minibuffer for editing.
the advantage of this above approach is that it offers user a
choice - continue using the same behaviour or press ’M-n’ to prefill
current file name.
next prev parent reply other threads:[~2022-05-30 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 3:24 bug#55267: 29.0.50; Provide customization to save project-find-file arg to savehist Pankaj Jangid
[not found] ` <handler.55267.B.165172109316668.ack@debbugs.gnu.org>
2022-05-05 3:50 ` bug#55267: Acknowledgement (29.0.50; Provide customization to save project-find-file arg to savehist) Pankaj Jangid
2022-05-05 7:28 ` bug#55267: 29.0.50; Provide customization to save project-find-file arg to savehist Juri Linkov
2022-05-12 16:38 ` Juri Linkov
2022-05-29 21:44 ` Dmitry Gutov
2022-05-30 6:08 ` Pankaj Jangid [this message]
2022-05-30 9:21 ` Dmitry Gutov
2022-05-29 21:42 ` Dmitry Gutov
2022-05-30 16:32 ` Juri Linkov
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=87ilpnh7rr.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=55267@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
/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).