From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexander Shukaev Newsgroups: gmane.emacs.help Subject: Re: Correct Paths to Emacs C Sources after Installation Date: Tue, 4 Nov 2014 00:05:47 +0100 Message-ID: References: <834mugvw5w.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1415055970 32510 80.91.229.3 (3 Nov 2014 23:06:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Nov 2014 23:06:10 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Nov 04 00:06:03 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1XlQhG-0007jv-TO for geh-help-gnu-emacs@m.gmane.org; Tue, 04 Nov 2014 00:06:03 +0100 Original-Received: from localhost ([::1]:37691 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlQhG-0007Z1-8M for geh-help-gnu-emacs@m.gmane.org; Mon, 03 Nov 2014 18:06:02 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlQh4-0007Yw-RK for help-gnu-emacs@gnu.org; Mon, 03 Nov 2014 18:05:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XlQh3-0006iu-SS for help-gnu-emacs@gnu.org; Mon, 03 Nov 2014 18:05:50 -0500 Original-Received: from mail-la0-x236.google.com ([2a00:1450:4010:c03::236]:45331) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlQh3-0006ii-6W for help-gnu-emacs@gnu.org; Mon, 03 Nov 2014 18:05:49 -0500 Original-Received: by mail-la0-f54.google.com with SMTP id s18so5050038lam.13 for ; Mon, 03 Nov 2014 15:05:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BbjpOiYd/CIYR0A2NET9ynLbX8zBRRJ6zMkhdl8kkKU=; b=OxnnHTmZl4npad9fukmVmTEp5jTHhsPyeddHLGvzcTqNafzgYWTsqhUyzv6u33+eJ6 HtDmY468mFw3xLORuNiobZA3hbM98EHOfeWRTscKGhxBi2O29H/c3nE1Bus3T7luZ3zy mOD/0Z8LWO2OnDhJ70CcAXMhznYiSdiVhX5UyGEkbVMRJUpVqAcva7VHExcMev8FhrkD gwwayUDZCgta6U3NmEwQhnXqmUDVsSj5xngdXxpx1c7sI+yV/bsqKsDiklvmzdls+qs9 00xM0CrqwseWeN98Ohdaw9brHIfoHYNGpbpUAcg/vN5p7iyxtzloXPlYXxezrY1n88k+ zRsw== X-Received: by 10.112.133.138 with SMTP id pc10mr54707515lbb.48.1415055947462; Mon, 03 Nov 2014 15:05:47 -0800 (PST) Original-Received: by 10.112.202.106 with HTTP; Mon, 3 Nov 2014 15:05:47 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::236 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:100705 Archived-At: Once again. I want to play around with interactive documentation feature of Emacs, i.e. clicking `C source code' links when searching for some implementation details. That would be particularly cool for people who like to hack on Emacs and actually, as I understand it, that's why such interactive feature was introduced in the first place. Two cases: 1. I build and install Emacs for personal usage. Does not even matter on what platform Unix-like or Windows. Sources are not installed by default, but I believe their either should or at least an option has to be provided for that. And Vsource_directory = Fexpand_file_name (build_string ("../"), Fcar (decode_env_path (0, PATH_DUMPLOADSEARCH, 0))); refers to a hard coded build directory path. Usually build directories are temporary and so after deleting it, one would not be able to browse C sources interactively. Furthermore, it is conceptually "stupid" to separate sources from built Emacs when, in fact, this built Emacs wants to refer to these sources it was built from. I think nobody can deny that it's pretty much a convention to distribute open-source project sources under ".../src/name" (for potential further usage or reference like we have in this case as well). 2. I build and install Emacs, then I package it and distribute to end users. Why on Earth should the path to the build directory (which obviously does not exist on end users' machines) that I used be hard coded into "Vsource_directory"? And again this leads us to the same argument as in #1. I thought these reasons were kind of obvious. What do you think of it?