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: Fri, 22 Jul 2016 13:48:38 +0200 Message-ID: References: <87wpke3kdj.fsf@russet.org.uk> <83h9biyek4.fsf@gnu.org> <877fce3flr.fsf@russet.org.uk> <83d1m6xint.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1469188206 20783 80.91.229.3 (22 Jul 2016 11:50:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Jul 2016 11:50:06 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 22 13:49:57 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 1bQYxn-000311-Se for ged-emacs-devel@m.gmane.org; Fri, 22 Jul 2016 13:49:56 +0200 Original-Received: from localhost ([::1]:46620 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQYxi-0002uS-9W for ged-emacs-devel@m.gmane.org; Fri, 22 Jul 2016 07:49:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40787) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQYwy-0002ka-Ti for emacs-devel@gnu.org; Fri, 22 Jul 2016 07:49:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQYwu-0003hJ-65 for emacs-devel@gnu.org; Fri, 22 Jul 2016 07:49:03 -0400 Original-Received: from hermes.netfonds.no ([80.91.224.195]:47725) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQYwt-0003gc-VB for emacs-devel@gnu.org; Fri, 22 Jul 2016 07:49:00 -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 1bQYwl-000162-AV for emacs-devel@gnu.org; Fri, 22 Jul 2016 13:48:57 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX9vCv+vyv+virfo1eo W0v+wi7+xjT+wS0HHiYZAAACcElEQVQ4jU2TMW/bMBCFT7ISrzqmDldJRTM7JeOsBki0s4DSWgOk 0mwiFfj3+46SEnMwDH56994dSaLb1ZXdsphp5yt/rnxV0bmqStnipDkxkZctbDpnq67FVozzPCQB Z1F4763vlO6HkFdWOCi8rLLVfdrAMe9Vrqp2VdkeBh3CJYQJUZqyabqcqWv1HGaAaZqoLJscsKEm x4wshS5QtDUvpFGKeZbtSRRUtMz4UpUFC+i3UtS2WqOrmt+NKZZIC6CWdV029YMx9te87cMcHqxU qQyAG1cHASgSuaV774DMSxgXgvQwxzD/eQiMv1sK5VTpeq2JrLNAx89aRHruE13JO9Sy5mUIl8Wc 9jrpmu/xuYfHaQ0FwFHzlR6zRQZrqYJ14lq68Dgqe/rqA3Fxjjt4e7gAjJuC66LpMrDendb+AGqw ohSweqxgn1I4pALAwsaeb8xj0ESPxmfJad7Mi5SG0Nc/bO4Qs9oOCnHRCBMioUOXwWWcRjQehjAk tgYK67Y+RirQ36FnnJ/kzSBMlwUMQ1T8YUGcNaKQMUoq1lA8ADhvjcw9Xzgo4gzwZGTqy+Fe5F7t 5YpE3CA5WFR7XRSjzIpl8nB3fzHH1xTzHVo8BD4a93b0/hkPZ85Ap5RZ8+48OvyJazYPAuSSRPm5 NwLe8PeAS0/bc2y77l0O961krePwBbCe5NhrnrGklHyrNuJOSkW8qTWujqrlVmgvr+og48qlWF6G vBJo8YnWw2qOIFBwXhg2S61bc9HW+i4c/iygRaFO3p9C/W9E7vhhdi9UKqnxKfleED3viABgvcWV pfQc5xR+iwerWxvEkPH9B49W663BF03XAAAAAElFTkSuQmCC In-Reply-To: (Lars Ingebrigtsen's message of "Fri, 22 Jul 2016 12:46:14 +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:206019 Archived-At: Lars Ingebrigtsen writes: > and jumping back and forth between the browser and Emacs to examine > and edit the code And Emacs is special in this regard. If what you're working on is $(web-framework-of-the-day), it there is little advantage to getting a bug report in your email client versus looking at it in a web browser. If you want to test some breaking code, you have to cut and paste it from where it is to where you want it to be and then test it. In Emacs, if a user says "(this-does-not-work) doesn't work", since what you're testing is what you're reading the bug report in, you can just execute it and see that it doesn't work and then fix it. In that sense, Emacs is a special snow flake. The unfortunate effect of this extreme ease (resulting from the high level of Emacs integration with everything) is that there's more stuff for new developers to get used to. If only debbugs had a sensible web interface, too, then it would be less daunting for new people, I think. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no