From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Vibhav Pant Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] ERC: support for IRCv3.1 CAP Date: Thu, 22 Sep 2016 21:36:36 +0530 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1474564777 16146 195.159.176.226 (22 Sep 2016 17:19:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Sep 2016 17:19:37 +0000 (UTC) Cc: "emacs-devel@gnu.org" To: Kelvin White Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 22 19:19:33 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bn7ee-0002YS-4J for ged-emacs-devel@m.gmane.org; Thu, 22 Sep 2016 19:19:24 +0200 Original-Received: from localhost ([::1]:54359 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn7ec-0000sa-6z for ged-emacs-devel@m.gmane.org; Thu, 22 Sep 2016 13:19:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn6Wd-0003BM-RU for emacs-devel@gnu.org; Thu, 22 Sep 2016 12:07:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bn6Wb-0004Ln-OE for emacs-devel@gnu.org; Thu, 22 Sep 2016 12:07:02 -0400 Original-Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]:32902) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn6WZ-00046H-Om; Thu, 22 Sep 2016 12:06:59 -0400 Original-Received: by mail-qk0-x233.google.com with SMTP id g67so20637672qkd.0; Thu, 22 Sep 2016 09:06:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+kRwOtBp8EvPlsFM1JV4lffOGPAI5DODS0X0qJE73B0=; b=Td9TcxLhMW0kDpwG9XMNv7cJCazPpLGGYg38IJWBHWBXyZdKB8oAu+sPTRD7FkDiVO 5wJq+mFaA48XiEMmc1uYu4Eu3IXNhY5OfEmQJmjaYZmC/m2QPE/PaQS6SIfhYs/Aen5t mYmfk8CXqchXpFojPVVtiZYNhOBTK3vtQfZUEcN14XZqhg/P6HOtp9dsXCK9s4YCEx/S 10SYjb+igNNGUmrzl6aFeSuUOdPk8SeDYrV7its/p2eZ9DVfs1xOJ0+B2GlTNk70bYhA KhVQhw74LaHABRWk6dp7UM1eOkbOZmLuIUgNYX7M3h+uc1gRlKWzTYafNWYvednuBKmc OMKQ== 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:from:date :message-id:subject:to:cc; bh=+kRwOtBp8EvPlsFM1JV4lffOGPAI5DODS0X0qJE73B0=; b=EByLUJDz9DJOqZg0f5u5cc5S6ay3ChM85MySaoKXU3Yd3dDvDs9EFio0cYIxfaDrQC a90/RirQE2KNsM3Sll8vKtq2qYHNXb14oxG/eABTrbsspUAdUrO0H83hr3tzwgRs4avj UlRAem9F04PJzHZ/WXFF9Ckeluv50BK1pYZMKqt3R1hhQXql27Jjiwq+vSXbPSIHJ4aY 73YwCgQBCn54urD9Op5kEQYcIm8Dbaper2T8xJyKOK0/RgOk5rWalLCb6+Ag0k44zGk9 JO5X7D9xAtaEybokTrjAAglkm6lq8Vtv/El1+JHDnInc6C2ftWsuqTXE5Ft1fY3NSmjN WUCg== X-Gm-Message-State: AA6/9Rkkh41H98nEEKhKw4EhvDO3sKrhAo6ErZnSoUeAkKYbCrzS3YmQv0Y5iy7x4+6WP01oRyEM/oqLkX5KaA== X-Received: by 10.55.97.130 with SMTP id v124mr2846124qkb.51.1474560397378; Thu, 22 Sep 2016 09:06:37 -0700 (PDT) Original-Received: by 10.140.81.165 with HTTP; Thu, 22 Sep 2016 09:06:36 -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::233 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:207705 Archived-At: Now that Emacs 25.1 is out, could this be reviewed again? I'd like to add support for more IRCv3 features (http://ircv3.net/irc/) for this development cycle. On Sat, Jun 25, 2016 at 7:34 PM, Vibhav Pant wrote: > 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? -- Vibhav Pant vibhavp@gmail.com