From: Kaushal Modi <kaushal.modi@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: Xue Fuqiao <xfq.free@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
Achim Gratz <Stromeko@nexgo.de>,
Emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] Add prettify symbols to python-mode
Date: Thu, 24 Sep 2015 06:33:09 -0400 [thread overview]
Message-ID: <CAFyQvY1ieh1E8ECAV6RERitufGXaimYOSETbywMMpSBXNxJzbw@mail.gmail.com> (raw)
In-Reply-To: <874mik6wqp.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
I believe that the "beginner" here in question is not someone who just
started using emacs but a beginner contributor who is already comfortable
with emacs and is interested in contributing to the C code but isn't
because there isn't enough "Getting started with C tinkering in emacs"
documentation.
I like the points that Xue made there with an example of what a "beginner"
would go through when trying to understand the display engine.
--
Kaushal Modi
On Sep 24, 2015 4:35 AM, "David Kastrup" <dak@gnu.org> wrote:
> Xue Fuqiao <xfq.free@gmail.com> writes:
>
> > BTW, I was just trying making an analysis of the this problem, and of
> > course my analysis could be wrong. Do you have any idea why newcomers
> > mostly prefer working on application-level code in Lisp?
>
> In my opinion that's a feature, not a bug. Elisp is there for a reason.
>
> > (Let's try and stay constructive. If we can find the causes, then we
> > have the possibility to improve the current condition.)
>
> We have Elisp exactly in order not to have to address problems by
> reverting to C programming. In my opinion it is entirely the wrong idea
> to have people start solving problems in C because they prefer it to
> Elisp. The main reason to solve problems in C is because there is no
> reasonably workable solution to be created in Elisp. If beginners turn
> to C first, they will not even know whether there would be a reasonably
> workable solution available in Elisp.
>
> Elisp code can be debugged reasonably nicely, manages its memory and
> data structures reliably. It's concise, memory-efficient and
> expressive.
>
> --
> David Kastrup
>
>
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
next prev parent reply other threads:[~2015-09-24 10:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 19:28 [PATCH] Add prettify symbols to python-mode Mark Oteiza
2015-09-20 22:48 ` Xue Fuqiao
2015-09-21 0:53 ` Mark Oteiza
2015-09-21 2:20 ` Stefan Monnier
2015-09-22 6:55 ` Richard Stallman
2015-09-22 12:44 ` Stefan Monnier
2015-09-22 14:42 ` Rasmus
2015-09-22 22:02 ` Richard Stallman
2015-09-23 6:22 ` Achim Gratz
2015-09-23 7:13 ` Eli Zaretskii
2015-09-23 8:04 ` David Kastrup
2015-09-23 14:12 ` Xue Fuqiao
2015-09-23 16:15 ` Eli Zaretskii
2015-09-23 16:52 ` David Kastrup
2015-09-23 17:09 ` Eli Zaretskii
2015-09-23 17:58 ` David Kastrup
2015-09-23 19:24 ` Eli Zaretskii
2015-09-23 19:39 ` David Kastrup
2015-09-23 19:48 ` Eli Zaretskii
2015-09-23 19:56 ` David Kastrup
2015-09-23 20:04 ` Eli Zaretskii
2015-09-23 20:10 ` David Kastrup
2015-09-23 19:38 ` Paul Eggert
2015-09-23 19:46 ` David Kastrup
2015-09-23 20:15 ` Paul Eggert
2015-09-23 21:40 ` David Kastrup
2015-09-24 1:16 ` Stephen J. Turnbull
2015-09-24 3:57 ` Xue Fuqiao
2015-09-24 14:31 ` Eli Zaretskii
2015-09-23 19:07 ` Achim Gratz
2015-09-23 19:42 ` Eli Zaretskii
2015-09-24 8:06 ` Xue Fuqiao
2015-09-24 8:35 ` David Kastrup
2015-09-24 10:33 ` Kaushal Modi [this message]
2015-09-24 14:32 ` Eli Zaretskii
2015-09-24 13:06 ` Xue Fuqiao
2015-09-24 14:32 ` Eli Zaretskii
2015-09-28 7:17 ` Dmitry Gutov
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=CAFyQvY1ieh1E8ECAV6RERitufGXaimYOSETbywMMpSBXNxJzbw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@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.