From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, 51180@debbugs.gnu.org, miha@kamnitnik.top
Subject: bug#51180: M-x emacs-lisp-byte-compile-and-load
Date: Fri, 15 Oct 2021 09:25:02 +0300 [thread overview]
Message-ID: <83pms6kdoh.fsf@gnu.org> (raw)
In-Reply-To: <E1mb97K-0006X9-3X@fencepost.gnu.org> (message from Richard Stallman on Thu, 14 Oct 2021 18:22:26 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Thu, 14 Oct 2021 18:22:26 -0400
> Cc: 51180@debbugs.gnu.org, miha@kamnitnik.top
>
> Is it worth having a function emacs-lisp-byte-compile-and-load?
It's a command, and we deemed it important enough to have it in the
Emacs-Lisp menu when the current buffer visits an Emacs Lisp file.
> It surely is not used often.
It is extremely useful when you work on some Lisp program and want to
test it in the same session.
> Does it simplify programs enough
> to outweigh the added complecity of defining and docuenting it?
Not programs, but interactive use of ELisp.
prev parent reply other threads:[~2021-10-15 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 11:27 bug#51180: 29.0.50; Non-compiled file loaded with M-x emacs-lisp-byte-compile-and-load miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-13 11:41 ` Lars Ingebrigtsen
2021-10-14 22:22 ` bug#51180: " Richard Stallman
2021-10-14 22:26 ` Lars Ingebrigtsen
2021-10-15 22:47 ` Richard Stallman
2021-10-14 22:48 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-15 6:25 ` Eli Zaretskii [this message]
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=83pms6kdoh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51180@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=miha@kamnitnik.top \
--cc=rms@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).