From: Emanuel Berg <incal@dataswamp.org>
To: 58797@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#58797: 29.0.50; Revise format of stored message tags in ERC
Date: Thu, 27 Oct 2022 09:46:48 +0200 [thread overview]
Message-ID: <87fsf9r9nb.fsf@dataswamp.org> (raw)
In-Reply-To: <87fsfa4t7j.fsf@neverwas.me>
J.P. wrote:
> Tags: patch
>
> I'm proposing we change the format (type) of the "tags"
> field in the `erc-response'
What is that, it's not a variable and it's not a function ...
> struct from
>
> (STRING . LIST)
>
> where LIST contains at most one (possibly empty) string, to
>
> (SYMBOL . OPT-STRING)
Well, as you know, symbol and string are object types in
Emacs, the use of the "OPT" prefix OTOH signals it's a name
and the purpose is to hold options, this mix isn't good IMO.
You can change OPT to OPTS perhaps, SYMBOL I don't know what
to change to since I don't know what symbols are intended to
be stored there ...
Also IMO the dotted list data structure is passé but if code
relies on it I don't suggest changing that just for the sake
of it ...
> For ERC 5.5 and Emacs 29
Okay, but isn't ERC built-in only or can you get "future"
version of ERC from GNU ELPA? Okay, that's it then, I see that
5.4.1 is avaliable there, I'm on
ERC 5.4.1 (IRC client for GNU Emacs 29.0.50)
But I use, as you see already, a very fresh Emacs, namely
GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, cairo
version 1.16.0) of 2022-10-09 [commit
a2dd9d683a02525183b5e692e42622c65639dda8]
so I guess I'm on the edge here :)
> Why bother?
To improve the software ...
> Isn't this a breaking change?
You can't make an omelet without hatching eggs ...
> Why now? Why not wait?
Do it today, in a different way!
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-10-27 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 13:20 bug#58797: 29.0.50; Revise format of stored message tags in ERC J.P.
2022-10-27 7:46 ` Emanuel Berg [this message]
2022-10-28 13:29 ` 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=87fsf9r9nb.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=58797@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 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.