From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Giap Tran <giaptx@mht.vn>,
Stephen Leake <stephen_leake@stephe-leake.org>,
49204@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#49204: 28.0.50; How to create new file in project by project-find-file
Date: Tue, 20 Jul 2021 21:34:27 -0400 [thread overview]
Message-ID: <jwv5yx43147.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ea4b33fd-23dd-ad23-47a5-b2497517cd76@yandex.ru> (Dmitry Gutov's message of "Wed, 21 Jul 2021 03:29:43 +0300")
Dmitry Gutov [2021-07-21 03:29:43] wrote:
> On 20.07.2021 05:58, Stefan Monnier via Bug reports for GNU Emacs, the Swiss
> army knife of text editors wrote:
>> I haven't followed the discussion, so I might be off, but I think what
>> is described above is something you can get simply by passing the
>> appropriate value for `mustmatch` to `completing-read` and friends
>> (including `read-file-name`).
> Probably not: most third-party completion functions out there don't support
> any non-nil values of that argument other than t (or treat them like t).
Their loss.
> And suppose we chose to use 'confirm', would a neutral prompt "Confirm"
> without clarification, as opposed to something like "File does not exist;
> Create?", be our best choice?
The same question comes up for `C-x C-f` (and `C-x C-b`).
So far the answer we have chosen is "yes". We can revisit it,
of course. Just like we may want to revisit the way `mustmatch` works,
but at least there is an existing "standard protocol" to get that kind
of behavior and I can't think of a good reason why `project-find-file`
should behave very differently from `find-file` in this respect.
Stefan
next prev parent reply other threads:[~2021-07-21 1:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 7:17 bug#49204: 28.0.50; How to create new file in project by project-find-file Giáp Trần
2021-06-27 0:07 ` Dmitry Gutov
2021-06-28 2:07 ` Giáp Trần
2021-06-29 13:49 ` Dmitry Gutov
2021-06-30 4:44 ` Giap Tran
2021-07-04 1:07 ` Dmitry Gutov
2021-07-05 4:03 ` Giap Tran
2021-07-18 0:46 ` Dmitry Gutov
2021-07-19 2:15 ` Giap Tran
2021-07-19 15:20 ` Juri Linkov
2021-07-20 2:15 ` Dmitry Gutov
2021-07-20 2:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-21 0:29 ` Dmitry Gutov
2021-07-21 1:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-08-02 11:37 ` Dmitry Gutov
2021-08-02 13:42 ` Giap Tran
2021-08-06 0:31 ` Dmitry Gutov
2021-07-20 2:18 ` 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=jwv5yx43147.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=49204@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=giaptx@mht.vn \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=stephen_leake@stephe-leake.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.