From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vibhav Pant Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] ERC: support for IRCv3.1 CAP Date: Sat, 25 Jun 2016 19:34:11 +0530 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1146ecc6fe483805361ac228 X-Trace: ger.gmane.org 1466863496 10736 80.91.229.3 (25 Jun 2016 14:04:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 25 Jun 2016 14:04:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kelvin White Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 25 16:04:55 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bGoCc-00059v-OS for ged-emacs-devel@m.gmane.org; Sat, 25 Jun 2016 16:04:55 +0200 Original-Received: from localhost ([::1]:50094 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGoCY-0006j9-Q9 for ged-emacs-devel@m.gmane.org; Sat, 25 Jun 2016 10:04:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGoC0-0006a8-9K for emacs-devel@gnu.org; Sat, 25 Jun 2016 10:04:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bGoBy-0005xn-9w for emacs-devel@gnu.org; Sat, 25 Jun 2016 10:04:15 -0400 Original-Received: from mail-qk0-x22c.google.com ([2607:f8b0:400d:c09::22c]:33489) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGoBw-0005xO-N1; Sat, 25 Jun 2016 10:04:12 -0400 Original-Received: by mail-qk0-x22c.google.com with SMTP id q79so27694112qke.0; Sat, 25 Jun 2016 07:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Bc4eInn0CNx11fwDMYirfwNIqJZTWglgT0GcgDoar34=; b=YKmQGKCCZIkBcXtD3UHFGyhK873rp9I8Av8sgzwUPI+MYBO+Hn6ey90W6vYXXbbLfw Qs6GMukp/WKOREja/9/IlSv0N0xc1+4XVGv5zisnGSpA88KnyE8t0uEzKS4TgiqCqahY 3BejVJAzLf3c3utXg9B6oqI85ZNHY8/UcJDfz9PuOFm6Fyii/prrqPX91zUGH0KlI5of QcO4UHqVmInIajRLliZsBSGUZFcL6q3+Tevu7u33N5Bg/GBI89O2NNMR3P8LfR8MB4NJ jcA2EO0wUqCHhWqtP5YXLnN54eoEIazUn3HQFU9PkvtWisxB9U3OFhk+G9gGpGR1rX3g fjnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Bc4eInn0CNx11fwDMYirfwNIqJZTWglgT0GcgDoar34=; b=F3Vefdm2T5Zm9zvVtIzGgWW8m8sjBjnhCAFTdaU2gRAkRjtrZ0rqRapcZh8zzWUIRl 8jkVYA+IIlgIktrEghB49j1vqK+hJnleJA1dTqhzklMtkJy+GnwfN7PgiTH4qg6K06Ef WONCFe42imPhiaSQysyB+StNTaIUSzXFmGRh++fyjbnF7pM4YWR47BB+Fs2+KTjFHzox mkEEVimPqRsoQCsyTn8Y0tHQF5hfZVRRQyPAjyySwIkSeTuUlquD2jHX1F5kEBNPsWNE g7iQWmPdFlvJcZvlXzubBR7EYJkJh43HyUK7g6obHy99GMH9ucKy8uM9Bbv76k+cDkbF LBOQ== X-Gm-Message-State: ALyK8tJ5O0UNSwNDamdK+dVmxrhUIBPUhyaheUUVpRu28P22smlneYK+avbL/1heMej33MnouZ3pDsTWDmqvzg== X-Received: by 10.55.26.102 with SMTP id a99mr7875042qka.145.1466863452045; Sat, 25 Jun 2016 07:04:12 -0700 (PDT) Original-Received: by 10.140.81.179 with HTTP; Sat, 25 Jun 2016 07:04:11 -0700 (PDT) Original-Received: by 10.140.81.179 with HTTP; Sat, 25 Jun 2016 07:04:11 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c09::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:204756 Archived-At: --001a1146ecc6fe483805361ac228 Content-Type: text/plain; charset=UTF-8 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" wrote: > On Tue, Jun 21, 2016 at 3:26 AM, Vibhav Pant 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? > --001a1146ecc6fe483805361ac228 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Most popular clients and servers have already started suppo= rting IRCv3, so I thought it would be a good idea to have some basic functi= onality for CAP in ERC. (Twitch already uses it to enable JOIN and PART mes= sages, 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 su= pport?
--001a1146ecc6fe483805361ac228--