Re: Cleaning up rcirc

[Philip Kaludercic]

Tassilo Horn <tsdh@gnu.org> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Either way, I also noticed there were other issues with the code, that
>> I have since fixed. Would it be ok to push the changes as a feature
>> branch, so that I don't have to re-send all the patches again and
>> again?
>
> IMHO, yes.  It would also make testing much easier.  I'm a rcirc user so
> I'd be happy to give it a whirl.

Just pushed the changes to feature/rcirc-update.

I rewrote the commits and remove the define-derived-mode change, because
that broke requiring more refactoring to fix.

A few IRCv3 specs have already been implemented, as listed in the new
option rcirc-implemented-capabilities. I plan to add these sooner or
later:

- https://ircv3.net/specs/extensions/account-notify
- https://ircv3.net/specs/extensions/account-tag
- https://ircv3.net/specs/extensions/extended-join
- https://ircv3.net/specs/extensions/away-notify
- https://ircv3.net/specs/extensions/echo-message
- https://ircv3.net/specs/extensions/labeled-response
- https://ircv3.net/specs/extensions/multiline
- https://ircv3.net/specs/extensions/sasl-3.1

and

- https://ircv3.net/specs/client-tags/reply
- https://ircv3.net/specs/client-tags/react
- https://ircv3.net/specs/extensions/chathistory

as soon as they become reliable. I have experimented with chathistory,
and in principle it works. What this would also require is a proper UI
to allow general queries. What is doable now is something like "request
the last 20 messages right after joining a new channel", and they will
be printed with the right timestamps.

-- 
        Philip K.