From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Thu, 20 Feb 2014 20:39:12 +0200 Message-ID: <53064BD0.7070009@yandex.ru> References: <52FCD2B4.5080006@yandex.ru> <52FD9F1D.50205@yandex.ru> <83mwhucg1h.fsf@gnu.org> <878ute589i.fsf@fencepost.gnu.org> <83d2iqc84m.fsf@gnu.org> <87wqgxkcr9.fsf@yandex.ru> <834n41db0d.fsf@gnu.org> <52FE2985.4070703@yandex.ru> <831tz5daes.fsf@gnu.org> <8738jlohd6.fsf@yandex.ru> <83txc1bl83.fsf@gnu.org> <5300189A.9090208@yandex.ru> <83wqgv9fbj.fsf@gnu.org> <20140216180712.236069f6@forcix.jorgenschaefer.de> <87wqgr4v18.fsf@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1392921576 3413 80.91.229.3 (20 Feb 2014 18:39:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Feb 2014 18:39:36 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, forcer@forcix.cx To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 20 19:39:45 2014 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 1WGYX6-0005mE-Rh for ged-emacs-devel@m.gmane.org; Thu, 20 Feb 2014 19:39:40 +0100 Original-Received: from localhost ([::1]:40177 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYX6-00082s-Cr for ged-emacs-devel@m.gmane.org; Thu, 20 Feb 2014 13:39:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYWz-00082X-Bs for emacs-devel@gnu.org; Thu, 20 Feb 2014 13:39:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGYWu-0008Aj-LT for emacs-devel@gnu.org; Thu, 20 Feb 2014 13:39:33 -0500 Original-Received: from mail-ee0-x22d.google.com ([2a00:1450:4013:c00::22d]:46038) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYWk-0007pf-Cv; Thu, 20 Feb 2014 13:39:18 -0500 Original-Received: by mail-ee0-f45.google.com with SMTP id b15so1122865eek.18 for ; Thu, 20 Feb 2014 10:39:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aTLrV+T8m68+AH1zeiK1+gJKo2O3G3HDE885VtEoSVk=; b=agODS8xIafZXaZ9R7tMl3cNwPv0W7uDKgGWWAiqNSqOShBz+dw8aTEXy7kezbmf978 Swm7zR7/ejY4i0p5OCVgpir+Ly9GBY9nHFNtOEFYpKfR3fDfn3ZE+kl56620jxfgif2O 4GyjVZY/8Ud8Yd5nwXTgv5RuWGcM7+6kh2nch49a50L81cNEIvedR6vhdRr5HjsSNDTb DsVwyS/YmNSVb4vE0w8YrMs5ck1FaL9KXhnZ7XPLB9IHOi/4cS+ySomaH2H3AvDRPcpZ KpXw6BTDSXTFpDH9j+3AUXjW4mFjy8y5rYkZlAprLTswB8JyJopWDlVRozVxYQcLGO7h XfSQ== X-Received: by 10.15.55.193 with SMTP id v41mr3566669eew.80.1392921556671; Thu, 20 Feb 2014 10:39:16 -0800 (PST) Original-Received: from [192.168.0.94] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id v6sm16894761eef.2.2014.02.20.10.39.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 10:39:15 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:169789 Archived-At: On 20.02.2014 20:13, Richard Stallman wrote: > Richard, have you tried discussing this with GCC developers recently? > > I don't follow you. What exactly is it you suggest I discuss with > them? I can discuss things with them, but to do so usefully I need > to know what issue to raise. You could discuss adding code completion, as a core GCC feature, or as an actively maintained plugin. Basically, you'd be able to call GCC with a certain argument, pass it the path to a file, line and column within it, and GCC would output a list of possible completions at that point (with some type information: e.g. if a completion is a function, it would include the arglist and the return type). It should also support receiving the contents of the file from stdin, because this way the buffer doesn't have to be saved, for code completion to work. Clang supports that. I couldn't find any real documentation for the format of the Clang completion output, but you can see some examples at the beginning of this page of this random forum thread: http://forums.codeblocks.org/index.php?topic=13559.15 > Considering your distaste for Clang, this page should look pretty > embarrassing: http://gcc.gnu.org/wiki/CodeCompletion > > I looked at it and saw no obvious point. However, I did not follow > the links because that would have taken me another day. No need. My point is, the wiki of the official GCC website "promotes" Clang because GCC itself lacks the respective feature.