all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "J.P." <jp@neverwas.me>
Cc: 57955@debbugs.gnu.org, emacs-erc@gnu.org
Subject: bug#57955: 29.0.50; Allow session-local ERC modules
Date: Tue, 20 Sep 2022 19:43:34 +0200	[thread overview]
Message-ID: <87r106eybd.fsf@gmx.de> (raw)
In-Reply-To: <8735cm2o2l.fsf__21117.726997339$1663692322$gmane$org@neverwas.me> (J. P.'s message of "Tue, 20 Sep 2022 06:05:38 -0700")

"J.P." <jp@neverwas.me> writes:

> Hi people,

Hi,

> Since its inception, ERC has aimed to support local modules, that is,
> modules local to a connection. (If you need convincing of this, take a
> look at `define-erc-module'.) This makes sense for a good many reasons,
> chief among them simplified semantics when arranging for buffer-local
> variables and hooks. Ancillary benefits include let-binding
> `erc-modules' around entry-point invocations and selectively disabling
> modules for particular sessions (e.g., after capability negotiation).

Without knowing erc in general and your patch in detail: this sounds
like you could profit from connection-local variables. Did you check
this?

> Thanks,
> J.P.

Best regards, Michael.





  reply	other threads:[~2022-09-20 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 13:05 bug#57955: 29.0.50; Allow session-local ERC modules J.P.
2022-09-20 17:43 ` Michael Albinus [this message]
2022-09-21 13:15   ` J.P.
     [not found] <8735cm2o2l.fsf@neverwas.me>
2022-10-26 13:16 ` J.P.
2022-11-15 15:07   ` J.P.
     [not found]   ` <877czww91p.fsf@neverwas.me>
2023-05-22  4:05     ` J.P.
2023-10-09  4:02 ` J.P.
     [not found] ` <87o7h8jvet.fsf@neverwas.me>
2023-10-14  0:23   ` J.P.
     [not found]   ` <87edhy9hne.fsf@neverwas.me>
2023-10-18 13:36     ` J.P.
2024-02-10 20:36 ` J.P.
     [not found] ` <87wmrcxdjf.fsf@neverwas.me>
2024-03-01  0:25   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r106eybd.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=57955@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 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.