From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55540@debbugs.gnu.org
Subject: bug#55540: 29.0.50; ERC launches autojoin-channels in current frame instead of original frame
Date: Fri, 20 May 2022 19:01:38 +0530 [thread overview]
Message-ID: <874k1kjpol.fsf@codeisgreat.org> (raw)
In-Reply-To: <87zgjc1hah.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 20 May 2022 15:10:14 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> This is somewhat related to bug#51753 -- how erc handles these buffer
> actions should be changed in general.
Thanks. Setting the value of erc-join-buffer to ’bury is a good
workaround. Found in that bug discussion.
What is the control command for marking the bug as duplicate? I couldn’t
locate such a command in "debbugs" package.
next prev parent reply other threads:[~2022-05-20 13:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 13:06 bug#55540: 29.0.50; ERC launches autojoin-channels in current frame instead of original frame Pankaj Jangid
2022-05-20 13:10 ` Lars Ingebrigtsen
2022-05-20 13:31 ` Pankaj Jangid [this message]
2022-05-20 13:37 ` Lars Ingebrigtsen
2022-05-23 1:56 ` bug#51753: ERC switches to channel buffer on reconnect J.P.
[not found] ` <87a6b92ers.fsf@neverwas.me>
2022-05-23 2:50 ` Pankaj Jangid
2022-05-23 7:48 ` J.P.
[not found] ` <87fsl0zo2e.fsf@neverwas.me>
2022-08-10 13:15 ` bug#51753: bug#55540: 29.0.50; ERC launches autojoin-channels in current frame J.P.
[not found] ` <87a68cnss7.fsf_-_@neverwas.me>
2022-08-11 2:55 ` Pankaj Jangid
[not found] ` <87sfm3tro1.fsf@codeisgreat.org>
2022-09-06 11:01 ` bug#51753: bug#55540: 29.0.50; ERC launches autojoin-channels in current frame instead of original frame Lars Ingebrigtsen
2022-09-06 11:01 ` Lars Ingebrigtsen
[not found] ` <87o7vsu5pc.fsf_-_@gnus.org>
2022-09-06 13:53 ` J.P.
2022-09-06 13:53 ` bug#51753: " J.P.
[not found] ` <87o7vs38yp.fsf@neverwas.me>
2022-09-06 14:02 ` Lars Ingebrigtsen
2022-09-07 3:10 ` J.P.
2022-09-07 3:10 ` J.P.
[not found] ` <874jxj282o.fsf@neverwas.me>
2022-09-07 12:55 ` bug#51753: " Lars Ingebrigtsen
2022-09-07 12:55 ` Lars Ingebrigtsen
[not found] ` <87mtbbmjho.fsf@gnus.org>
2022-09-20 13:11 ` J.P.
2022-09-20 13:11 ` bug#51753: " J.P.
[not found] ` <87pmfq198w.fsf@neverwas.me>
2022-09-22 3:07 ` Pankaj Jangid
2022-09-22 3:07 ` Pankaj Jangid
[not found] ` <87y1uc150p.fsf@codeisgreat.org>
2022-09-22 6:22 ` bug#51753: " J.P.
2023-04-08 23:25 ` J.P.
2023-04-08 23:25 ` J.P.
[not found] ` <87pmg77tpc.fsf@dataswamp.org>
2022-12-30 14:28 ` J.P.
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=874k1kjpol.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=55540@debbugs.gnu.org \
--cc=larsi@gnus.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 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).