From: Michael Heerdegen <michael_heerdegen@web.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>, 36917@debbugs.gnu.org
Subject: bug#36917: 27.0.50; debbugs-gnu: Don't hardcode switch-to-buffer
Date: Wed, 21 Aug 2019 14:41:02 +0200 [thread overview]
Message-ID: <87wof64roh.fsf@web.de> (raw)
In-Reply-To: <87d0h2plim.fsf@gmail.com> (Noam Postavsky's message of "Sun, 18 Aug 2019 10:59:29 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> > Use 'pop-to-buffer-same-window' instead of 'switch-to-buffer' to
> > display bug reports so user can configure behavior via
> > 'display-buffer-alist' (Bug#36917).
> >
> > * packages/debbugs/debbugs-gnu.el (debbugs-gnu-show-reports): Use
> > 'pop-to-buffer-same-window' to display bug reports.
>
> I think you can combine these two paragraphs.
Done.
> > I didn't have a look at the other remaining `switch-to-buffer' calls.
> > Noam, did you mean to substitute all of them?
>
> If you think you might want to control the buffer switching of those
> other functions with display-buffer-alist, then yes.
I've installed the single change for now. I'm not familiar with the
rest of the package, so I would want to leave that to the authors.
Thanks,
Michael.
next prev parent reply other threads:[~2019-08-21 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 2:35 bug#36917: 27.0.50; debbugs-gnu: Don't hardcode switch-to-buffer Michael Heerdegen
2019-08-04 11:07 ` Michael Albinus
2019-08-05 6:29 ` Michael Heerdegen
2019-08-05 6:36 ` Michael Albinus
2019-08-13 15:37 ` Noam Postavsky
2019-08-18 12:24 ` Michael Heerdegen
2019-08-18 12:35 ` Michael Albinus
2019-08-18 22:55 ` Eric Abrahamsen
2019-08-18 14:59 ` Noam Postavsky
2019-08-21 12:41 ` Michael Heerdegen [this message]
2019-08-21 19:06 ` Michael Albinus
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=87wof64roh.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=36917@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=npostavs@gmail.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).