From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83461 invoked by alias); 12 Jan 2018 22:04:20 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 83433 invoked by uid 89); 12 Jan 2018 22:04:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=HTo:U*kawa, insights, savannah X-HELO: aibo.runbox.com Received: from aibo.runbox.com (HELO aibo.runbox.com) (91.220.196.211) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 12 Jan 2018 22:04:17 +0000 Received: from [10.9.9.211] (helo=mailfront11.runbox.com) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1ea7Qs-0004lM-QM for kawa@sourceware.org; Fri, 12 Jan 2018 23:04:14 +0100 Received: from 70-36-239-2.dsl.dynamic.fusionbroadband.com ([70.36.239.2] helo=localhost.localdomain) by mailfront11.runbox.com with esmtpsa (uid:757155 ) (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) id 1ea7Qm-0004jF-Oo for kawa@sourceware.org; Fri, 12 Jan 2018 23:04:09 +0100 To: Kawa mailing list From: Per Bothner Subject: language server protocol for Kawa Message-ID: <78c36015-ce0d-a0cf-c81e-37f0ce4d8e9a@bothner.com> Date: Fri, 12 Jan 2018 22:04:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-q1/txt/msg00006.txt.bz2 Has anyone done any work for a Language Server Protocol (https://langserver.org/) for Kawa? Any insights or partial code? I ask because I'm getting ready to jump into this as the next major project for Kawa. (I do have one non-trivial bug It want to resolve first: GitLab issue #33 and Savannah bug #52390, which are probably both related to the fix for issue #11). -- --Per Bothner per@bothner.com http://per.bothner.com/