From: Fu Yuan <casouri@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Install C source code for for debugging help
Date: Fri, 27 Sep 2019 18:45:07 -0400 [thread overview]
Message-ID: <4F3CD911-4F73-4C64-9EB5-23ED639E6DBB@gmail.com> (raw)
In-Reply-To: <CAM-tV-92rYbwPHO8ObD-KQih9aOYzzjNG_iOns5qwS54y=F_Mw@mail.gmail.com>
I’m not sure this change worth the effort.
I’m not sure being able to C source is that much beneficial to normal users as the C source isn’t that easy to make sense of, as opposed to Elisp sources.
Regarding the encourage effect Stefan mentioned, I think Elisp sources already have this effect and is better than C source in this aspect because it’s easier to understand, manipulate and play around with.
It is possible that because people on this list all know internal C source of Emacs well, you exaggerated the effect of it for normal users.
On the other hand, maybe a command that downloads and stores the appropriate C source could be added. This shouldn’t be very hard to implement and don’t effect the build size. And people that wants to see the C source can achieve it very easily with the help of this command.
So what I’m trying to say is that 1) Emacs is already encouraging users to explore (Elisp) source and 2) enabling access to C by default don’t have much benefit and 3) there might be a good alternative.
Just my two cents.
- Yuan
next prev parent reply other threads:[~2019-09-27 22:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:37 Install C source code for for debugging help Paul Eggert
2019-09-27 5:07 ` Eli Zaretskii
2019-09-27 6:13 ` Paul Eggert
2019-09-27 7:19 ` Eli Zaretskii
2019-09-27 13:01 ` Stefan Monnier
2019-09-27 13:12 ` Stefan Monnier
2019-09-27 13:33 ` Eli Zaretskii
2019-09-27 13:48 ` Stefan Monnier
2019-09-27 13:56 ` Eli Zaretskii
2019-09-27 14:24 ` Paul Eggert
2019-09-27 14:40 ` Eli Zaretskii
2019-09-28 4:03 ` Paul Eggert
2019-09-27 17:04 ` Noam Postavsky
2019-09-27 22:45 ` Fu Yuan [this message]
2019-09-28 0:09 ` Juanma Barranquero
2019-09-28 2:14 ` Michael Rohleder
2019-09-27 15:25 ` Stefan Monnier
2019-09-28 1:32 ` Richard Stallman
2019-09-28 2:06 ` Jean-Christophe Helary
2019-09-27 15:03 ` Lars Ingebrigtsen
2019-09-27 15:47 ` David Ringo
2019-09-27 8:37 ` Andreas Schwab
2019-09-27 9:06 ` Eli Zaretskii
2019-09-27 11:58 ` Andreas Schwab
2019-09-27 12:58 ` Eli Zaretskii
2019-09-27 13:45 ` Andreas Schwab
2019-09-27 13:50 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-09-28 18:19 Angelo Graziosi
2019-09-29 6:56 ` Paul Eggert
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=4F3CD911-4F73-4C64-9EB5-23ED639E6DBB@gmail.com \
--to=casouri@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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.