unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "J.P." <jp@neverwas.me>
To: 67767@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#67767: 30.0.50; ERC 5.6: Add track integration to the nicks module
Date: Mon, 11 Dec 2023 18:18:17 -0800	[thread overview]
Message-ID: <87msug17va.fsf__9977.24528876773$1702347549$gmane$org@neverwas.me> (raw)
In-Reply-To: <87edfs3gj4.fsf@neverwas.me> (J. P.'s message of "Mon, 11 Dec 2023 07:28:15 -0800")

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

> [2] Users will have to toggle the module's minor-mode to update the
>     variable mid-session, but we can provide a Custom :set function to
>     help with this. Also, there's actually a resource penalty that comes
>     with this change too. We can probably use per-server instead of
>     per-channel hash tables, or only go per-channel if a local value for
>     `erc-track-faces-normal-list' exists on `erc-track-mode' init.

It turns out these changes may require more planning than originally
budgeted. There's a growing dependency on aspects of the `button' module
that haven't been fully sorted, along with a rather heightened potential
for leaking memory, so I'd rather not move too hastily without good
reason. As such, I'll likely be putting a hold on this until 5.7 and
retitling the bug accordingly.





  reply	other threads:[~2023-12-12  2:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 15:28 bug#67767: 30.0.50; ERC 5.6: Add track integration to the nicks module J.P.
2023-12-12  2:18 ` J.P. [this message]
2023-12-12 14:49 ` J.P.
2023-12-13 14:06 ` J.P.
     [not found] ` <8734w6yz76.fsf@neverwas.me>
2023-12-18 14:51   ` J.P.
2024-09-30  0:34 ` J.P.
     [not found] ` <87ed52q8rd.fsf@neverwas.me>
2024-10-04  8:30   ` J.P.
     [not found]   ` <87ldz4b77j.fsf@neverwas.me>
2024-10-05  1:40     ` J.P.
2024-10-15  3:02     ` 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='87msug17va.fsf__9977.24528876773$1702347549$gmane$org@neverwas.me' \
    --to=jp@neverwas.me \
    --cc=67767@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).