From: Lars Ingebrigtsen <larsi@gnus.org>
To: Emacs Watcher <emacswatcher@gmail.com>
Cc: 32285@debbugs.gnu.org, brettg@posteo.net
Subject: bug#32285: 26.1;
Date: Wed, 23 Oct 2019 11:09:24 +0200 [thread overview]
Message-ID: <87v9sfkeuz.fsf@gnus.org> (raw)
In-Reply-To: <CA+h+dP-+__D53UHYQdsc9PVW5WooQ9F+ehvK5vWP-iG_YPTXkg@mail.gmail.com> (Emacs Watcher's message of "Fri, 27 Jul 2018 07:53:17 -0700")
Emacs Watcher <emacswatcher@gmail.com> writes:
> You should notice that the 'freenode' buffer has been reused and that the
> original session cannot be reached. My guess is that this is an original ERC
> design limitation, but it probably ought to be addressed.
It looks like it does this on purpose: It a server buffer exists, and
it's connected to the server you're using, then it's reused:
;; if buf-name is taken by a different connection (or by something !erc)
;; then see if "buf-name/server" meets the same criteria
(dolist (candidate (list buf-name (concat buf-name "/" server)))
(if (and (not buffer-name)
erc-reuse-buffers
(or (not (get-buffer candidate))
(or target
(with-current-buffer (get-buffer candidate)
(and (erc-server-buffer-p)
(not (erc-server-process-alive)))))
(with-current-buffer (get-buffer candidate)
(and (string= erc-session-server server)
(erc-port-equal erc-session-port port)))))
(setq buffer-name candidate)))
If you don't want this, then erc-reuse-buffers should be set to nil,
apparently.
So this doesn't seem to be a bug, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-10-23 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 1:41 bug#32285: 26.1; Emacs Watcher
2018-07-27 3:25 ` Brett Gilio
2018-07-27 14:53 ` Emacs Watcher
2018-07-28 12:20 ` bug#32285: erc loses access to original session when connecting again to same host Noam Postavsky
2019-10-23 9:09 ` Lars Ingebrigtsen [this message]
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=87v9sfkeuz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=32285@debbugs.gnu.org \
--cc=brettg@posteo.net \
--cc=emacswatcher@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).