all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Brent Goodrick <bgoodr@gmail.com>, 2061@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org,
	bug-submit-list@donarmstrong.com
Subject: bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file
Date: Mon, 26 Jan 2009 11:31:24 -0500	[thread overview]
Message-ID: <E1LRUMu-0007EK-NT@fencepost.gnu.org> (raw)
In-Reply-To: <18813.7599.138907.415045@hungover.brentg.com> (message from Brent Goodrick on Sun, 25 Jan 2009 18:19:27 -0800)

    When would the user ever prefer to load the .elc file after having
    modified the .el file?

If you have written changes which are incomplete and not ready
to be executed.

This feature gives you control over when to start running your
changes: you control it by when you compile the files.  It is
important and it is easy to use.







  parent reply	other threads:[~2009-01-26 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  2:19 bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file Brent Goodrick
2009-01-26  4:08 ` Eli Zaretskii
2009-01-27 15:08   ` Brent Goodrick
2009-01-26  8:45 ` Juanma Barranquero
2009-01-27 15:54   ` Brent Goodrick
2009-01-28  2:06     ` Juanma Barranquero
2009-01-28  8:29       ` Kevin Rodgers
2009-02-02 16:07       ` Brent Goodrick
2009-01-26 16:31 ` Richard M Stallman [this message]
2009-01-27 15:56   ` Brent Goodrick
  -- strict thread matches above, loose matches on Subject: below --
2009-01-27  0:49 Stefan Monnier
2009-02-02 18:56 ` Juanma Barranquero
2009-02-03  9:59 ` Richard M Stallman
2009-02-03 21:07   ` Stefan Monnier

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=E1LRUMu-0007EK-NT@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=2061@emacsbugs.donarmstrong.com \
    --cc=bgoodr@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug-submit-list@donarmstrong.com \
    --cc=emacs-pretest-bug@gnu.org \
    /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.