unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: "Przemysław Wojnowski" <esperanto@cumego.com>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] CONTRIBUTE - writing tests for understanding internals
Date: Tue, 10 Nov 2015 14:58:55 -0800	[thread overview]
Message-ID: <m2fv0dwjf4.fsf@Vulcan.attlocal.net> (raw)
In-Reply-To: <87twotqxme.fsf@cumego.com> ("Przemysław Wojnowski"'s message of "Tue, 10 Nov 2015 23:48:41 +0100")

>>>>> Przemysław Wojnowski <esperanto@cumego.com> writes:

+There are at least two good ways to understand Emacs Internal.
+
+One of them is to read the code, but the nodes "Tips" and "GNU Emacs
+Internals" in the Appendix of the Emacs Lisp Reference Manual may also
+help.  Some source files, such as xdisp.c, have large commentaries
+describing the design and implementation in more detail.
+
+Another way into Emacs Internal is to write tests. This one is more
+fun, takes you through Emacs contribution process and increases
+Emacs test coverage! Don't think twice!

Just some word smithing:

    There are at least two good ways to start getting familiar with the
    internals of Emacs:
    
    One is to read the code. Some source files, such as xdisp.c, have large
    commentaries describing the design and implementation in more detail.
    Another is to visit the nodes "Tips" and "GNU Emacs Internals" in the
    Appendix of the Emacs Lisp Reference Manual.
    
    Yet Another way is to write tests. This can be a lot of fun, introduces
    you to the Emacs contribution process, and increases Emacs test coverage!
    Don't think twice! If you want to jump in, this is a great way to start.

John



  reply	other threads:[~2015-11-10 22:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 22:48 [PATCH] CONTRIBUTE - writing tests for understanding internals Przemysław Wojnowski
2015-11-10 22:58 ` John Wiegley [this message]
2015-11-11  3:36 ` Eli Zaretskii
2015-11-11  7:45   ` Przemysław Wojnowski
2015-11-11  8:26     ` Andreas Röhler
2015-11-11 15:40       ` Eli Zaretskii
2015-11-11 15:40     ` Eli Zaretskii
2015-11-11 21:08       ` Przemysław Wojnowski
2015-11-11 21:26         ` Eli Zaretskii
2015-11-11 21:36           ` John Wiegley
2015-11-12  3:40             ` Eli Zaretskii
2015-11-11 21:48           ` Przemysław Wojnowski
2015-11-12  7:16       ` Andreas Röhler
2015-11-12 16:15         ` Eli Zaretskii
2015-11-12 20:03           ` Stephen Leake
2015-11-12 20:40             ` Andreas Röhler
2015-11-12 20:55               ` Eli Zaretskii
2015-11-12 21:42                 ` Przemysław Wojnowski
2015-11-13  7:33                   ` Eli Zaretskii
2015-11-13  8:03                     ` Andreas Röhler

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=m2fv0dwjf4.fsf@Vulcan.attlocal.net \
    --to=jwiegley@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=esperanto@cumego.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 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).