From: "J.P." <jp@neverwas.me>
To: 63569@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#63569: 30.0.50; ERC 5.6: Add automatic nickname highlighting to ERC
Date: Mon, 13 Nov 2023 12:06:46 -0800 [thread overview]
Message-ID: <87h6lpzacp.fsf__40864.0353869245$1699906127$gmane$org@neverwas.me> (raw)
In-Reply-To: <87r0l1frzc.fsf@neverwas.me> (J. P.'s message of "Tue, 07 Nov 2023 08:28:07 -0800")
"J.P." <jp@neverwas.me> writes:
> A user on Libera requested some time ago that pool-creation facilities
> like the ones mentioned above be added to erc-nicks. The attached patch
> does this but in a simplified manner that avoids adding additional user
> options. Instead, it defaults to the "blind eye" approach mentioned
> above since (IMO) it's likeliest to meet user expectations.
>
> The patch also adds two ready-made Custom choice variants to the option
> `erc-nick-colors': `font-lock' and `ansi-color'. These are predefined
> sets of candidates for the (repeat string) :type variant. As may be
> obvious, ERC interprets these symbols as palettes to be populated from
> the :foreground colors of whatever font-lock- and ansi-color-related
> faces exist for the current theme.
>
> There's also a minor bug fix involving initialization ordering.
This has been installed as
5baa0f61f8d * Offer alternate pool-creation strategies in erc-nicks
next prev parent reply other threads:[~2023-11-13 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ilcp1za1.fsf@neverwas.me>
2023-05-23 13:37 ` bug#63569: 30.0.50; ERC 5.6: Add automatic nickname highlighting to ERC J.P.
2023-05-30 14:24 ` J.P.
2023-06-13 4:07 ` J.P.
[not found] ` <87r0qgknt1.fsf@neverwas.me>
2023-06-16 3:07 ` Richard Stallman
[not found] ` <E1q9zoC-0003PO-Jf@fencepost.gnu.org>
2023-06-16 5:12 ` J.P.
[not found] ` <87h6r8j8ie.fsf@neverwas.me>
2023-06-18 2:13 ` Richard Stallman
2023-06-22 13:47 ` J.P.
[not found] ` <871qi3boca.fsf@neverwas.me>
2023-06-23 13:38 ` J.P.
[not found] ` <87wmzu8fjg.fsf@neverwas.me>
2023-06-26 13:44 ` J.P.
2023-07-01 3:31 ` J.P.
2023-07-14 2:37 ` J.P.
2023-09-07 13:31 ` J.P.
[not found] ` <87zg1yjeib.fsf@neverwas.me>
2023-11-07 16:28 ` J.P.
[not found] ` <87r0l1frzc.fsf@neverwas.me>
2023-11-13 20:06 ` J.P. [this message]
2023-05-18 14:37 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='87h6lpzacp.fsf__40864.0353869245$1699906127$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=63569@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).