From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: xfq.free@gmail.com, Stromeko@nexgo.de, dak@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Add prettify symbols to python-mode
Date: Thu, 24 Sep 2015 17:32:51 +0300 [thread overview]
Message-ID: <83a8sbkhv0.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY1ieh1E8ECAV6RERitufGXaimYOSETbywMMpSBXNxJzbw@mail.gmail.com>
> Date: Thu, 24 Sep 2015 06:33:09 -0400
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Cc: Achim Gratz <Stromeko@nexgo.de>, Xue Fuqiao <xfq.free@gmail.com>,
> Emacs-devel <emacs-devel@gnu.org>, Eli Zaretskii <eliz@gnu.org>
>
> 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.
In general, the level of documentation (or lack thereof) about the
internals is about the same in C and in Lisp, so I don't understand
why this is seen as a problem for C hacking, but not for Lisp.
> 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.
As I wrote in response, those points are all but covered already,
starting with CONTRIBUTE, so the perceived lack of information seems
to be largely an illusion.
next prev parent reply other threads:[~2015-09-24 14:32 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
2015-09-24 14:32 ` Eli Zaretskii [this message]
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=83a8sbkhv0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--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.