From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: A couple of things that I think should be in byte bytecode meta comments Date: Sat, 23 Dec 2017 10:32:28 -0500 Message-ID: References: <83o9mqlin0.fsf@gnu.org> <83h8sildcd.fsf@gnu.org> <83fu81luke.fsf@gnu.org> Reply-To: rswgnu@gmail.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114a7166d7b228056103a5ec" X-Trace: blaine.gmane.org 1514043118 27051 195.159.176.226 (23 Dec 2017 15:31:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 23 Dec 2017 15:31:58 +0000 (UTC) Cc: emacs-devel To: Rocky Bernstein Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 23 16:31:54 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eSlm9-0006Ma-5t for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2017 16:31:49 +0100 Original-Received: from localhost ([::1]:45328 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSlo7-0007vt-MR for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2017 10:33:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44084) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSlnR-0007uN-Oy for emacs-devel@gnu.org; Sat, 23 Dec 2017 10:33:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSlnP-0006Po-KF for emacs-devel@gnu.org; Sat, 23 Dec 2017 10:33:09 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44366) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSlnH-0006Il-E0; Sat, 23 Dec 2017 10:32:59 -0500 Original-Received: from mail-qk0-f182.google.com ([209.85.220.182]:40022) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1eSlnH-00073e-7W; Sat, 23 Dec 2017 10:32:59 -0500 Original-Received: by mail-qk0-f182.google.com with SMTP id q14so25168733qke.7; Sat, 23 Dec 2017 07:32:59 -0800 (PST) X-Gm-Message-State: AKGB3mJm4ahsbcrOKnj5K1K5nMDfRI6yZ4xEQN5Mo3AnN2tEIFx+u7QV aR53Ph5ofrUVbpYsfZepo/CQZtiz2vgHSpQQAQM= X-Google-Smtp-Source: ACJfBotAdMtI+naxAdlKvmKQ7cu008VNWy4e6gyX4i/5Ooax8xvHAj7Q+HVJ66risZxsDbOEB49IeuiHBDrLZRHDOlE= X-Received: by 10.55.80.8 with SMTP id e8mr7378515qkb.126.1514043178724; Sat, 23 Dec 2017 07:32:58 -0800 (PST) Original-Received: by 10.200.55.124 with HTTP; Sat, 23 Dec 2017 07:32:28 -0800 (PST) In-Reply-To: X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:221384 Archived-At: --001a114a7166d7b228056103a5ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Dec 23, 2017 at 3:44 AM, Rocky Bernstein wrote: > > Path names give you good places to start looking for the file. > > And often they can quickly give information as to what's up, e.g. I am > running from the stable or development branch. Or running from an Ubuntu > build or a source-code build. > =E2=80=8BIf you are actually running a branch of Emacs and using a .elc fil= e included therein, then =E2=80=8Byour load-path should be configured to take= you to the proper associated source file with the find-library command, unless filenames are duplicated within the lisp tree. Only uses outside of that, i.e. working on files outside of the branch you are running, would this be an issue, I would think, or if there ever is a bundled format of .elc that combines the byte-compiled output of multiple files. If anything of this nature is ever done, it should be based on the source file's default installed location relative to the Emacs root directory for portability. Any reasonable function/tool could then find the source file. Bob --001a114a7166d7b228056103a5ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Dec 23, 2= 017 at 3:44 AM, Rocky Bernstein <rocky@gnu.org> = wrote:

Path names give you good places t= o start looking for the file.

And often they can quickly give information as to what's up, e.g. I am=20 running=C2=A0 from the stable or development branch. Or running from an=20 Ubuntu build or a source-code build.

=E2= =80=8BIf you are actually running a branch of Emacs and using a .elc file i= ncluded therein, then =E2=80=8Byour load-path should be configured to take = you to the proper associated source file with the find-library command, unl= ess filenames are duplicated within the lisp tree.=C2=A0 Only uses outside = of that, i.e. working on files outside of the branch you are running, would= this be an issue, I would think, or if there ever is a bundled format of .= elc that combines the byte-compiled output of multiple files.

If any= thing of this nature is ever done, it should be based on the source file= 9;s default installed location relative to the Emacs root directory for por= tability.=C2=A0 Any reasonable function/tool could then find the source fil= e.

Bob


--001a114a7166d7b228056103a5ec--