From: Lars Ingebrigtsen <larsi@gnus.org>
To: Christian Kruse <cjk@defunct.ch>
Cc: emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Wed, 20 Jul 2016 16:44:24 +0200 [thread overview]
Message-ID: <m3a8hc2wtz.fsf@gnus.org> (raw)
In-Reply-To: <874m7k5qmv.fsf@defunct.ch> (Christian Kruse's message of "Wed, 20 Jul 2016 16:30:00 +0200")
Christian Kruse <cjk@defunct.ch> writes:
> I think he has a point: it is *very* hard to get into Emacs
> coding. I tried it more than once but failed. Documentation seems very
> distributed (for a look here, for b look over there, ...), a clear
> step-by-step guide to get a build environment including running tests
> seems to be missing. E.g. why is there no "contribute" document on the
> shiny new website?
Yeah, I agree that the documentation for getting started is rather
distributed. And the recipe (on GNU/Linux systems) is so trivial.
It would be nice to have it emphasised just how easy it is somewhere
central, like:
----
Cut and paste these five lines and you have a complete working Emacs
that you can hack and send patches to:
sudo apt-get build-dep emacs24
git clone git://git.savannah.gnu.org/emacs.git
cd emacs
make
./src/emacs &
Send patches via `M-x report-emacs-bug'. Happy hacking!
----
Of course, if you want to make larger changes then you have to know
about ChangeLog formats and assignments and testing and etc etc etc, but
for people starting out, hacking on and contributing to Emacs is so easy
it's kinda difficult to believe, which is perhaps why people imagine it
to be difficult. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-07-20 14:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 13:54 Development suggestions from an ENSIME developer Lars Ingebrigtsen
2016-07-20 14:02 ` Clément Pit--Claudel
2016-07-22 22:48 ` Robert Cochran
2016-07-23 7:30 ` Eli Zaretskii
2016-07-23 9:00 ` Lars Ingebrigtsen
2016-07-23 19:52 ` Richard Stallman
2016-07-23 13:50 ` Clément Pit--Claudel
2016-07-23 20:14 ` Phillip Lord
2016-07-25 18:34 ` Robert Cochran
2016-08-03 6:05 ` John Wiegley
2016-08-06 18:42 ` Alex Dunn
2016-07-20 14:03 ` Dmitry Gutov
2016-07-20 14:08 ` Lars Ingebrigtsen
2016-07-20 14:12 ` Dmitry Gutov
2016-07-20 14:23 ` Christian Kruse
2016-07-20 14:41 ` Dmitry Gutov
2016-07-20 14:30 ` Christian Kruse
2016-07-20 14:44 ` Lars Ingebrigtsen [this message]
2016-07-20 15:02 ` Clément Pit--Claudel
2016-07-20 15:07 ` Lars Ingebrigtsen
2016-07-20 15:31 ` Clément Pit--Claudel
2016-07-20 17:00 ` Stefan Monnier
2016-07-21 18:40 ` Phillip Lord
2016-07-21 19:30 ` Eli Zaretskii
2016-07-21 20:22 ` Stefan Monnier
2016-07-21 21:26 ` Christian Kruse
2016-07-21 22:04 ` Dmitry Gutov
2016-07-21 20:23 ` Phillip Lord
2016-07-21 20:50 ` joakim
2016-07-22 6:59 ` Eli Zaretskii
2016-07-22 10:46 ` Lars Ingebrigtsen
2016-07-22 11:48 ` Lars Ingebrigtsen
2016-07-22 13:00 ` Robert Weiner
2016-07-22 13:34 ` Eli Zaretskii
2016-07-22 14:28 ` Robert Weiner
2016-07-22 14:45 ` Ted Zlatanov
2016-07-22 13:35 ` Stefan Monnier
2016-07-22 14:38 ` Eli Zaretskii
2016-07-22 14:56 ` Stefan Monnier
2016-07-22 15:58 ` Phillip Lord
2016-07-22 15:47 ` Phillip Lord
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=m3a8hc2wtz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=cjk@defunct.ch \
--cc=emacs-devel@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.
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.