Re: Development suggestions from an ENSIME developer

[Lars Ingebrigtsen <larsi@gnus.org>]

Lars Ingebrigtsen <larsi@gnus.org> 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