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: progmodes/project.el and search paths Date: Tue, 29 Dec 2015 04:00:37 +0200 Message-ID: <5681E945.8020702@yandex.ru> References: <55BE209F.1000009@siege-engine.com> <55BE509B.2080307@yandex.ru> <55C166EF.9060909@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1451354471 16937 80.91.229.3 (29 Dec 2015 02:01:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2015 02:01:11 +0000 (UTC) To: Eric Ludlam , Emacs Development Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 03:00:57 2015 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 1aDjaq-0003Mc-O9 for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2015 03:00:56 +0100 Original-Received: from localhost ([::1]:46834 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDjap-0007H6-VZ for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 21:00:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44273) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDjae-0007Gy-6M for emacs-devel@gnu.org; Mon, 28 Dec 2015 21:00:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDjab-0004mm-0m for emacs-devel@gnu.org; Mon, 28 Dec 2015 21:00:44 -0500 Original-Received: from mail-wm0-x22c.google.com ([2a00:1450:400c:c09::22c]:38716) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDjaa-0004me-Px for emacs-devel@gnu.org; Mon, 28 Dec 2015 21:00:40 -0500 Original-Received: by mail-wm0-x22c.google.com with SMTP id l126so287151778wml.1 for ; Mon, 28 Dec 2015 18:00:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=wzJZ+aelzsZgw5e8ohm1uuFdwnp8evIAda2l05VV/aI=; b=pmaAPrIpvQoD767wx6PDFT1nGww0O7Ft+QEJs6LxkLTlN9n7OYULscBXUKur4HSTck VBJUBE0z4f54oVu9IsEdAUL9C/fr+NS5p8EMaR1fNlP/8pL5jps3uRGLG8S6DaeOt3Of Id2pZdC3vuI0IezaZtDKbwcCNcVF34s0IQbpDENt2Oh0IpHRDn/9HgsnfRsfKc7Y6fjH NlmerDga1KxEc5EXCmERL7wOgEoHqSYTYfyabIO8faz91FFX6D71O4bHrJrWmRWlUjGc bWYc65JOqZWvIs7R1Gz7JB4RpiKjXt0ANfIcmTqIYjD7dFdxq7rQid3ucY3Z5gpkEb44 XmZg== X-Received: by 10.194.20.5 with SMTP id j5mr618707wje.71.1451354439875; Mon, 28 Dec 2015 18:00:39 -0800 (PST) Original-Received: from [192.168.1.2] ([185.105.175.24]) by smtp.googlemail.com with ESMTPSA id e136sm51051339wma.23.2015.12.28.18.00.38 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Dec 2015 18:00:39 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0 In-Reply-To: <55C166EF.9060909@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::22c 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:197057 Archived-At: Hi Eric, On 08/05/2015 04:29 AM, Eric Ludlam wrote: > The attached is my experience of things I either needed in EDE's base > classes to implement a project, or that some tool needed, and what I > learned along the way. You might think it is too EDE specific, but I > put in only the most basic stuff, and put in things I kind of wish I had > time to add to EDE. I've put a list of TODO items into project.el. It's less ambitious than your list, but hopefully it covers the essentials that we (together with the community) will be able to consistently implement across the board. I have omitted certain useful things like "jump from 'include' statement in C++ to the file" and "navigating between code and doc" because they seem to require separate (though related) facilities that we're yet to design.