[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs terminology (not again!?) [was: Apologia for bzr]

From: Tom
Subject: Re: Emacs terminology (not again!?) [was: Apologia for bzr]
Date: Fri, 10 Jan 2014 19:10:42 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

David Reitter <david.reitter <at> gmail.com> writes:
> At this time, my concrete suggestion I would have is to make semantic, CEDET 
and etags work out-of-the-box for all major programming paradigms, and make 
them work without noticeable performance penalty. 

I'd suggest giving some attention to Eclim too. It can do things which
other tools cannot AFAIK. E.g. offering code fixes and stuff. See here:


Of course, it requires Eclipse, but it's not necessarily a disadvantage,
because lots of users use Eclipse today and they try emacs beside that.
So it can even be an advantage, because the user can work in eclipse
as usual and at the same time he can work with the same project in
emacs. It makes very easy to try working in emacs, because the user
does not have to create a new environment for developing with emacs,
emacs simply connects to the running eclipse instance.

And Eclim has lots of low hanging fruits, so it can be improved 
with little effort. It only needs some attention, because the current
maintainer said he wouldn't implement stuff he didn't use:


So a polished/improved Eclim would be very useful for newbie users
even if it's not part of core Emacs, because it makes easy to
try working in emacs.

Here's a list of what Eclim is capable of, and only a fraction of
this is implemented by the emacs interface, though it's not hard
to implement them (it involves only calling the relevant operations
and presenting the results to the user):

Eclipse Projects

Create, update, and delete Eclipse projects.
Easily manage Eclipse .classpath files (support for maven and ivy).
Quickly and easily manage settings globally or on a project basis.


Automatic source code validation (w/ visual marking of errors and warnings).
Context sensitive code completion.
Code correction suggestions with option to apply a suggestion.
Class constructor generation.
Java Bean getter and setter generation.
Generation of delegate methods.
Java source and java doc searching capabilities.
Generate stub methods from implemented interfaces or super classes.
Generate stub methods for junit testing.
Quickly clean and sort imports and easily import new classes.
Automatic generation of logging initialization code, upon first usage of a 
Javadoc generation for package, class, field, method, etc.
Java regular expression testing.
Support for Checkstyle.
Validation of log4j xml files.


Context sensitive code completion.
Source code validation.

Context sensitive code completion.
Source code validation.


Context sensitive code completion.
Automatic validation (w/ visual marking of errors and warnings).


Support for creating android projects


Ant execution from any file.
Context sensitive code completion when editing build files.
Automatic validation of build files (w/ visual marking of errors and warnings).
Quick access to ant documentation.


Maven execution from any file.
Maven repository searching and ability to add results to pom file.


File validation using jsl.


Code completion.
Source code validation.


Context sensitive code completion.
Find element definition support.
Regular expression testing.
Django functionality.
Validation via python compiler, pyflakes, and pylint.


Context sensitive code completion.
Source code validation.

Xml / Dtd / Xsd

Automatic validation (w/ visual marking of errors and warnings).
Quickly look up element definition from the current xml file's dtd or xsd.
Context sensitive code completion.

And more...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]