all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: Rocky Bernstein <rocky@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
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	[thread overview]
Message-ID: <CA+OMD9j4ywqE2AeLkDa2k9QyWwLZ8DyLw8qif0=D7CPdYvCmWg@mail.gmail.com> (raw)
In-Reply-To: <CANCp2gYp5xhndOT7vNOqaNmmN50qzQ5NV0Uvi9i4pRhDXqHMuQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Sat, Dec 23, 2017 at 3:44 AM, Rocky Bernstein <rocky@gnu.org> 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.
>

​If you are actually running a branch of Emacs and using a .elc file
included therein, then ​your 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

[-- Attachment #2: Type: text/html, Size: 2127 bytes --]

  reply	other threads:[~2017-12-23 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 17:54 A couple of things that I think should be in byte bytecode meta comments Rocky Bernstein
2017-12-22 17:55 ` Rocky Bernstein
2017-12-22 18:30   ` Eli Zaretskii
2017-12-22 18:49     ` Rocky Bernstein
2017-12-22 20:25       ` Eli Zaretskii
2017-12-22 20:55         ` Rocky Bernstein
2017-12-23  8:25           ` Eli Zaretskii
2017-12-23  8:44             ` Rocky Bernstein
2017-12-23 15:32               ` Robert Weiner [this message]
2017-12-23 17:16                 ` Rocky Bernstein
2017-12-23 18:30                   ` Robert Weiner
2017-12-24  2:44                     ` Rocky Bernstein
2018-01-13 19:44                       ` Thien-Thi Nguyen
2017-12-22 21:27 ` Andreas Schwab
2017-12-22 21:43   ` Rocky Bernstein
2017-12-23  8:25     ` Andreas Schwab
2017-12-23  8:35       ` Rocky Bernstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+OMD9j4ywqE2AeLkDa2k9QyWwLZ8DyLw8qif0=D7CPdYvCmWg@mail.gmail.com' \
    --to=rsw@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rocky@gnu.org \
    --cc=rswgnu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.