From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Byte compilation without writing the .elc file
Date: Sun, 23 Jun 2019 08:55:53 -0400 [thread overview]
Message-ID: <jwv4l4g1mwm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: m3o92ov7p5.fsf@gnus.org
> Often when I'm working on an out-of-tree Emacs Lisp file, I want to do
> byte compilation to see whether what I've done generates any warnings --
> but I don't want the .elc file, because I want to run it from .el.
Have you tried `flymake-mode`?
Stefan
next prev parent reply other threads:[~2019-06-23 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 11:53 Byte compilation without writing the .elc file Lars Ingebrigtsen
2019-06-23 12:55 ` Stefan Monnier [this message]
2019-06-23 13:35 ` Lars Ingebrigtsen
2019-06-23 13:14 ` Clément Pit-Claudel
2019-06-23 13:38 ` Lars Ingebrigtsen
2019-06-23 13:32 ` phillip.lord
2019-06-23 15:49 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4l4g1mwm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).