From: Mike Kazantsev <mk.fraggod@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: 59976@debbugs.gnu.org, emacs-erc@gnu.org
Subject: bug#59976: ERC 5.4.1: erc-networks--id gets clobbered in erc server buffer on /query name conflict
Date: Thu, 15 Dec 2022 23:45:52 +0500 [thread overview]
Message-ID: <20221215234552.76f2a2f5__22845.4600017116$1671130040$gmane$org@malediction> (raw)
In-Reply-To: <20221215232455.4a9c6677@malediction>
On Thu, 15 Dec 2022 23:24:55 +0500
Mike Kazantsev <mk.fraggod@gmail.com> wrote:
> Come to think of it, I'd probably also add the most obvious effect of :id
> for naming the server buffer, i.e. something like this:
>
> When present, ID should be an opaque object for identifying the connection
> unequivocally, and will correspond to name of the created erc server buffer
> after connection. ...
>
> Can probably be phrased better, but since main effect of "(erc ...)" command is
> creating that server buffer, what it will be named seem to be an important detail
> (if only for finding it afterwards).
In fact, I think allowing for naming server buffers how you want them
to be named with one easy and reasonably-obvious option should probably
be most prominent thing about it:
https://e.var.nz/scr-20221215233955.jpg
(example of using :id for all networks, in contrast to earlier
inconsistent not-entirely-local naming)
--
Mike Kazantsev // fraggod.net
next prev parent reply other threads:[~2022-12-15 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 19:00 bug#59976: ERC 5.4.1: erc-networks--id gets clobbered in erc server buffer on /query name conflict Mike Kazantsev
2022-12-12 14:35 ` J.P.
[not found] ` <87pmcowuzv.fsf@neverwas.me>
2022-12-12 15:35 ` Mike Kazantsev
[not found] ` <20221212203508.3cd44bb6@malediction>
2022-12-13 15:13 ` J.P.
2022-12-15 14:16 ` J.P.
[not found] ` <87sfhgn45z.fsf@neverwas.me>
2022-12-15 18:24 ` Mike Kazantsev
[not found] ` <20221215232455.4a9c6677@malediction>
2022-12-15 18:45 ` Mike Kazantsev [this message]
2022-12-16 15:17 ` 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='20221215234552.76f2a2f5__22845.4600017116$1671130040$gmane$org@malediction' \
--to=mk.fraggod@gmail.com \
--cc=59976@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
/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).