From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tom Tromey <tromey@redhat.com>
Cc: 6836@debbugs.gnu.org
Subject: bug#6836: 23.2; ERC -vs- uniquify
Date: Sun, 27 Dec 2015 22:54:21 +0100 [thread overview]
Message-ID: <87k2nz7e2a.fsf@gnus.org> (raw)
In-Reply-To: <m3sk2mearg.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 10 Aug 2010 09:40:51 -0600")
Tom Tromey <tromey@redhat.com> writes:
> I have uniquify-buffer-name-style set to post-forward-angle-brackets.
>
> In ERC I connect to multiple servers, which sometimes have the same
> channel names. For example I have two "#gdb" channels I join.
>
> The channel buffers are named #gdb and #gdb<2> -- but I would prefer
> something based on the server name instead. Ideally, ERC and uniquify
> would work together to achieve this.
I think this was fixed in 2011. If there's more than one server, the
second one gets called "buf-name/server"...
So I'm closing this bug report. If this is still a problem in Emacs
25.1, please reopen.
;; Reuse existing buffers, but not if the buffer is a connected server
;; buffer and not if its associated with a different server than the
;; current ERC buffer.
;; 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
(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)))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2015-12-27 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 15:40 bug#6836: 23.2; ERC -vs- uniquify Tom Tromey
2012-04-12 8:18 ` bug#6836: bug #6836 " Binjo
2015-12-27 21:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2nz7e2a.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6836@debbugs.gnu.org \
--cc=tromey@redhat.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 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.