From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Thu, 20 Feb 2014 19:45:31 +0100 Organization: Organization?!? Message-ID: <87ha7tr5bo.fsf@fencepost.gnu.org> References: <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> <53064BD0.7070009@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392921958 8104 80.91.229.3 (20 Feb 2014 18:45:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Feb 2014 18:45:58 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 20 19:46:06 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 1WGYdG-0007Rv-9s for ged-emacs-devel@m.gmane.org; Thu, 20 Feb 2014 19:46:02 +0100 Original-Received: from localhost ([::1]:40194 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYdF-0001rx-Un for ged-emacs-devel@m.gmane.org; Thu, 20 Feb 2014 13:46:01 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53493) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYd5-0001jt-TV for emacs-devel@gnu.org; Thu, 20 Feb 2014 13:45:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGYcz-0001pf-NL for emacs-devel@gnu.org; Thu, 20 Feb 2014 13:45:51 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:41421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGYcz-0001pT-Ft for emacs-devel@gnu.org; Thu, 20 Feb 2014 13:45:45 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WGYcw-0006wT-Vv for emacs-devel@gnu.org; Thu, 20 Feb 2014 19:45:42 +0100 Original-Received: from x2f47c6d.dyn.telefonica.de ([2.244.124.109]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Feb 2014 19:45:42 +0100 Original-Received: from dak by x2f47c6d.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Feb 2014 19:45:42 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 24 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f47c6d.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:0BCXZ+m6NpHJI0H0SGaKEayJpHY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:169790 Archived-At: Dmitry Gutov writes: > 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). I think it would make sense to pass that info via pipe or socket and receive the output similarly. That way each file only needs to get parsed once, not repeatedly for every completion. -- David Kastrup