From: Vibhav Pant <vibhavp@gmail.com>
To: Kelvin White <kwhite@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] ERC: support for IRCv3.1 CAP
Date: Sat, 25 Jun 2016 19:34:11 +0530 [thread overview]
Message-ID: <CA+T2Sh3Jf2aNS5BZJcD0d0uPx8NhUngSxY-w40R=3x-3wA4jYA@mail.gmail.com> (raw)
In-Reply-To: <CAG-q9=ZLaLOZ+ZZKGcZgX1X6+C1__WFTUsKUsd6NH6jJaLTBhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Most popular clients and servers have already started supporting IRCv3, so
I thought it would be a good idea to have some basic functionality for CAP
in ERC. (Twitch already uses it to enable JOIN and PART messages, necessary
for building the user list for a channel)
On 21 Jun 2016 20:52, "Kelvin White" <kwhite@gnu.org> wrote:
> On Tue, Jun 21, 2016 at 3:26 AM, Vibhav Pant <vibhavp@gmail.com> wrote:
> >
> > The IRCv3.1 specification adds the CAP command, allowing
> > client/servers to enable/disable certain capabilities. The following
> > patch adds the CAP command, and the response handler for CAP LS, LIST,
> > REQ, ACK, NAK and error 410 (ERR_INVALIDCAPCMD) messages.
> >
>
> I'm not sure that this is needed. Why does ERC need to implement CAP
> support?
>
[-- Attachment #2: Type: text/html, Size: 1135 bytes --]
next prev parent reply other threads:[~2016-06-25 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 7:26 [PATCH] ERC: support for IRCv3.1 CAP Vibhav Pant
2016-06-21 15:22 ` Kelvin White
2016-06-25 14:04 ` Vibhav Pant [this message]
2016-09-22 16:06 ` Vibhav Pant
2016-09-22 17:35 ` Kelvin White
2016-09-22 17:51 ` John Wiegley
2016-09-22 18:00 ` Vibhav Pant
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='CA+T2Sh3Jf2aNS5BZJcD0d0uPx8NhUngSxY-w40R=3x-3wA4jYA@mail.gmail.com' \
--to=vibhavp@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kwhite@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.