From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Development suggestions from an ENSIME developer Date: Wed, 20 Jul 2016 16:44:24 +0200 Message-ID: References: <874m7k5qmv.fsf@defunct.ch> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1469025931 2025 80.91.229.3 (20 Jul 2016 14:45:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 Jul 2016 14:45:31 +0000 (UTC) Cc: emacs-devel@gnu.org To: Christian Kruse Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 20 16:45:21 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bPskQ-0004MG-Se for ged-emacs-devel@m.gmane.org; Wed, 20 Jul 2016 16:45:19 +0200 Original-Received: from localhost ([::1]:35006 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPskP-00053y-Tq for ged-emacs-devel@m.gmane.org; Wed, 20 Jul 2016 10:45:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPsjs-00053h-5X for emacs-devel@gnu.org; Wed, 20 Jul 2016 10:44:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPsjn-0005IZ-4N for emacs-devel@gnu.org; Wed, 20 Jul 2016 10:44:43 -0400 Original-Received: from hermes.netfonds.no ([80.91.224.195]:42039) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPsjm-0005IN-Td for emacs-devel@gnu.org; Wed, 20 Jul 2016 10:44:39 -0400 Original-Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1bPsji-0006ni-S7; Wed, 20 Jul 2016 16:44:37 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEU6DxUtBw5raFFROTM6 JiYTAwYBYRdJAAACSElEQVQ4jWWTsXLsIAxFsb3uTfD2WSA9Rri3ge1hbf7/VyKEs8mbp4JhOIN0 dRFs9lLJ/0IBK4dcpvhvCPkZWWmR38sVrGRou6kuI57ksYH0ok0a6rqUAmm9wMHM0JkBujGlz7QA UxPerMBOMCyWgekSTGBgsOx+AQOrHQDG1Atm4ADTavwAUcQACeBYFgIwGIPLwFgZD9wbYFUcST1L RF2u9fEsA6kqvCuv06PGPlKXXyU1MJnio4NjfYXwdMe+OKEJsFuxTj2kQDutRke91E+6wQpopeT5 EYKsVlupd44gxjPIBhwe1mgguLM4t4qlF946qaW1isDb+GE+z1k+fS/lhiAxNjbU38QRLHgLcsNu UzddwP8+rY4sf8ivK1mIQXjvvI8yEsCm871UeSL44D4sgSIkYD815l1EBAECgRlTPjIvvMzPI/ZQ gY3XlPDMazwP6JUOOlgHF6gx8V0Yr7TXKPgNGL9FBLvXzmvbAK+ibjiAHT92L51tgPONFMUA+/3c yHoC7FbfLc8AwPkZ0d0KlGWYYkQDTwA38wnIjwtgCrwCYFCZoz9AqTD3QkbBhoBZAhIB5nYEdO1l 9g1gKqhVyz2LFRpQdOMHoCwmOwS2gXbD1oca8ctxLlpx1W7Y6jr3ciWgCFBxWC9Q7tgI/AJb9eYX Ah5iDH+ArnoPfPuc++0vUGS9fFQzt1utctWQdRQKgY6xevwDaBh8HaPZTH8B/ezXAw3wj/QLbBu5 4xP/3Lww+waygYwgsWV7A3S6DRyqzoNzLdU3jZ3wXNhYgzYAAAAASUVORK5CYII= In-Reply-To: <874m7k5qmv.fsf@defunct.ch> (Christian Kruse's message of "Wed, 20 Jul 2016 16:30:00 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205884 Archived-At: Christian Kruse 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