From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs C tutorial
Date: Fri, 07 Nov 2014 09:01:31 +0200 [thread overview]
Message-ID: <83wq77sddg.fsf@gnu.org> (raw)
In-Reply-To: <87lhnnvgtp.fsf@debian.uxu>
> From: Emanuel Berg <embe8573@student.uu.se>
> Date: Fri, 07 Nov 2014 04:18:42 +0100
>
> The thing is, C isn't very practical. :)
>
> C is great as a system language. It is very low-level
> (at least nowadays one would say), very fast, very
> straightforward... And this role, it has in Emacs as
> well!
>
> You should use C for stuff that will be implemented
> once and then seldom if ever touched. It is not for
> interactive trial-and-error fine-tuning.
>
> Lisp on the other hand is highly interactive, not at
> all kernel-like and "you should never notice it"
> bu-hoo arms down. In a way, Lisp is much more playful
> and alive. And that's why it is much closer to the
> user and why so many users, eh, use it!
>
> So for users to improve Emacs by means of its C is
> like burning down the house to kill the rats. Not to
> mention, in practice that would be very unpleasant,
> having to recompile for every tiny change. For this
> reason alone, if I were to use C for each change and
> extention to the Emacs UX, that would make me not do
> it...
Even if all of the above were correct and accurate (which it isn't),
someone who wants to add or modify Emacs primitives written in C must
work on that level.
So knowing where to find the information the OP talked about is still
important, and, yes, very practical.
prev parent reply other threads:[~2014-11-07 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:07 Emacs C tutorial E Sabof
2014-10-31 21:29 ` Eli Zaretskii
2014-10-31 23:50 ` E Sabof
2014-11-01 8:15 ` Eli Zaretskii
2014-11-01 8:53 ` E Sabof
2014-11-01 9:22 ` Eli Zaretskii
2014-11-01 16:59 ` Aurélien Aptel
2014-11-01 17:15 ` Eli Zaretskii
2014-11-01 18:22 ` E Sabof
[not found] ` <mailman.12491.1414799441.1147.help-gnu-emacs@gnu.org>
2014-11-01 5:17 ` Barry Margolin
2014-11-01 15:25 ` Bruno Félix Rezende Ribeiro
2014-11-01 18:20 ` E Sabof
[not found] ` <mailman.12540.1414866048.1147.help-gnu-emacs@gnu.org>
2014-11-07 3:18 ` Emanuel Berg
2014-11-07 7:01 ` 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=83wq77sddg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).