From: "J.P." <jp@neverwas.me>
To: 57955@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#57955: 29.0.50; Allow session-local ERC modules
Date: Fri, 13 Oct 2023 17:23:01 -0700 [thread overview]
Message-ID: <87edhy9hne.fsf__41207.4924259045$1697243046$gmane$org@neverwas.me> (raw)
In-Reply-To: <87o7h8jvet.fsf@neverwas.me> (J. P.'s message of "Sun, 08 Oct 2023 21:02:02 -0700")
I've added something similar to the proposed change as
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d46c016f
If you'll recall, I initially left this bug open as a reminder that we
still lack a solution to the glaring problem of configuration scoping.
To summarize, this concerns the pressing need to allow users to specify
different values for new (and hopefully existing) global options based
on context (like network, channel, speaker, etc.). One idea bandied
about has been adapting connection-local variables to be more abstract
and eventually integrating them with Customize and `use-package'. As
thing stand, though, each local module must itself decide whether it's
session-local, buffer-local, or both. And it must contend with stashing
and restoring its configured state on its own.
I'll likely close this bug after opening another to address these
broader configuration concerns. Thanks.
next prev parent reply other threads:[~2023-10-14 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8735cm2o2l.fsf@neverwas.me>
2022-10-26 13:16 ` bug#57955: 29.0.50; Allow session-local ERC modules 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. [this message]
[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.
2022-09-20 13:05 J.P.
2022-09-20 17:43 ` Michael Albinus
2022-09-21 13:15 ` 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='87edhy9hne.fsf__41207.4924259045$1697243046$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=57955@debbugs.gnu.org \
--cc=emacs-erc@gnu.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).