From: "J.P." <jp@neverwas.me>
To: Emanuel Berg <incal@dataswamp.org>
Cc: bug-gnu-emacs@gnu.org, emacs-erc@gnu.org
Subject: Re: bug#58797: 29.0.50; Revise format of stored message tags in ERC
Date: Fri, 28 Oct 2022 06:29:39 -0700 [thread overview]
Message-ID: <87k04knkjg.fsf@neverwas.me> (raw)
In-Reply-To: <87fsf9r9nb.fsf@dataswamp.org> (Emanuel Berg's message of "Thu, 27 Oct 2022 09:46:48 +0200")
Emanuel Berg <incal@dataswamp.org> writes:
> 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 ...
Um, I guess by "type" I meant something more like `:type' in the broader
"describing the shape of some field" sense. Not so much (info "(elisp)
Lisp Data Types") or what have you. Apologies for the confusion.
>> 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 ...
Poor choice of descriptive label on my part, clearly. I didn't mean to
suggest a custom user option but rather something like a
NIL-OR-NONEMPTY-STRING. IOW, whatever might satisfy a `typep' spec of
'(cons symbol (or null (and string (not (string 0)))))
or similar (bastardized pseudo-CL notwithstanding).
>> 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)
The releases on ELPA are basically snapshots of lisp/erc taken whenever
the ";; Version: " header changes. So, the work you see on HEAD is still
unreleased. It's possible that incrementing the version ahead of time
(like to 5.5-git or something) would make that clearer, but AFAIK we
can't do that without triggering yet another release. Hope that makes
sense.
prev parent reply other threads:[~2022-10-28 13:29 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
2022-10-28 13:29 ` J.P. [this message]
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=87k04knkjg.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-erc@gnu.org \
--cc=incal@dataswamp.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.