From: Juri Linkov <juri@linkov.net>
To: Giap Tran <giaptx@mht.vn>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
49204@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#49204: 28.0.50; How to create new file in project by project-find-file
Date: Mon, 19 Jul 2021 18:20:04 +0300 [thread overview]
Message-ID: <87k0lmqu8r.fsf@mail.linkov.net> (raw)
In-Reply-To: <d4687516-1c49-95df-1d0d-861220caf008@mht.vn> (Giap Tran's message of "Mon, 19 Jul 2021 09:15:10 +0700")
>> How can we know? Do you mean that it tells you that by asking to confirm
>> after you press RET?
>
> I mean we have to looks by our eyes :P
>
> Oh, you mentioned "confirm". Do you use magit? I see this package has
> a good UI/UX by default. If the user wants to push to a new branch is not
> exist, magit will a "confirm" question.
The same way as switch-to-buffer confirms a non-existent buffer with:
C-x b non-existent TAB RET [Confirm]
next prev parent reply other threads:[~2021-07-19 15:20 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 [this message]
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
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=87k0lmqu8r.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=49204@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=giaptx@mht.vn \
--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.