From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eshel Yaron <me@eshelyaron.com>, 65387@debbugs.gnu.org
Subject: bug#65387: [PATCH] New user option 'submit-emacs-patch-display-help'
Date: Thu, 16 Nov 2023 09:25:36 +0200 [thread overview]
Message-ID: <86bkbutb0v.fsf@mail.linkov.net> (raw)
In-Reply-To: <86wmxqp12h.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 20 Aug 2023 19:37:18 +0300")
>>> I don't know if it justifies a new option, as you say, and I don't mind
>>> keeping a modified `submit-emacs-patch` in my config.
>>
>> Let's see what others think about this new command.
>>
>> Would people please voice their opinions about adding it?
>
> If 'submit-emacs-patch' used 'pop-to-buffer-same-window'
> instead of 'switch-to-buffer' like in the patch below,
> then using such simple config would be possible:
>
> (add-to-list 'display-buffer-alist
> '("\\*Patch Help\\*"
> display-buffer-no-window
> (allow-no-window . t)))
>
> @@ -509,7 +509,7 @@ submit-emacs-patch
> (list (read-string (format-prompt "This patch is about" guess)
> nil nil guess)
> file)))
> - (switch-to-buffer "*Patch Help*")
> + (pop-to-buffer-same-window "*Patch Help*")
Now pushed. And maybe this could be closed?
next prev parent reply other threads:[~2023-11-16 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 19:33 bug#65387: [PATCH] New user option 'submit-emacs-patch-display-help' Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 19:58 ` Eli Zaretskii
2023-08-19 20:56 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 6:07 ` Eli Zaretskii
2023-08-20 7:56 ` Visuwesh
2023-08-20 9:59 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 11:35 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 16:37 ` Juri Linkov
2023-11-16 7:25 ` Juri Linkov [this message]
2023-12-15 1:12 ` Stefan Kangas
2023-09-06 17:47 ` Stefan Kangas
2023-09-06 18:31 ` Eli Zaretskii
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=86bkbutb0v.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=65387@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=me@eshelyaron.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).