From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Process to build standalone Emacs + deps in Windows
Date: Thu, 26 Mar 2020 14:19:13 +0100 [thread overview]
Message-ID: <86blojtfse.fsf@csic.es> (raw)
In-Reply-To: jwv369v4w4x.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Of course, we do not need the *.el files at all.
>
> I really hope we keep them there. Even if many users won't look at
> them, the fact that they're so easy to get to is almost a defining
> feature of Emacs.
I concur that the *.el files _are_ needed. Right now I am debugging 3
regressions in Emacs-27 and a bug in 26.3. I can do this with the
installed copy of Emacs without needing to install the sources (even
though I have them in other directories) because I can inspect the
code. Moreover, the current information system about variables and
functions is dramatically improved by having them around: I can use C-h
v and name a variable and go to the code and see how it is used,
etc. Without the *.el files Emacs becomes just a black box, like VS
Studio.
--
Juan José García Ripoll
http://juanjose.garciaripoll.com
http://quinfog.hbar.es
next prev parent reply other threads:[~2020-03-26 13:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 13:03 Process to build standalone Emacs + deps in Windows Juan José García Ripoll
2020-03-22 13:59 ` Eli Zaretskii
2020-03-22 14:38 ` Juan José García-Ripoll
2020-03-22 17:25 ` Eli Zaretskii
2020-03-22 18:54 ` Phillip Lord
2020-03-22 19:35 ` Eli Zaretskii
2020-03-22 21:02 ` Phillip Lord
2020-03-23 3:23 ` Eli Zaretskii
2020-03-23 23:36 ` Phillip Lord
2020-03-24 3:27 ` Eli Zaretskii
2020-03-24 18:21 ` Phillip Lord
2020-03-25 12:50 ` Juan José García-Ripoll
2020-03-25 14:43 ` Juan José García-Ripoll
2020-03-25 14:54 ` Juan José García-Ripoll
2020-03-25 15:33 ` Eli Zaretskii
2020-03-25 16:41 ` Juan José García-Ripoll
2020-03-25 17:03 ` Eli Zaretskii
2020-03-25 17:22 ` Juan José García-Ripoll
2020-03-25 17:34 ` Eli Zaretskii
2020-03-25 22:40 ` Phillip Lord
2020-03-26 13:16 ` Juan José García-Ripoll
2020-03-26 14:32 ` Eli Zaretskii
2020-03-26 22:20 ` Phillip Lord
2020-03-25 22:34 ` Phillip Lord
2020-03-26 3:49 ` Stefan Monnier
2020-03-26 13:19 ` Juan José García-Ripoll [this message]
2020-03-26 22:16 ` Phillip Lord
2020-03-26 13:24 ` Juan José García-Ripoll
2020-03-26 14:37 ` Eli Zaretskii
2020-03-28 16:01 ` Juan José García-Ripoll
2020-03-28 16:23 ` Eli Zaretskii
2020-03-28 19:36 ` Phillip Lord
2020-03-28 19:41 ` Eli Zaretskii
2020-03-26 22:28 ` Phillip Lord
2020-03-25 15:25 ` Eli Zaretskii
2020-03-22 18:58 ` Phillip Lord
2020-03-22 18:32 ` phillip.lord
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=86blojtfse.fsf@csic.es \
--to=juanjose.garciaripoll@gmail.com \
--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).