Hi ymnk,

Atsuhiko Yamanaka wrote:
For your conveniences, I'll reformat the code with it at formal 0.1.29 
release timing, but please keep in your mind that, that format definition may 
be changed and I'll not promise to reformat the code at every release.
I'm working a committer of Eclipse.org, but I'm not an Eclipse user.
I can not write the code without Emacs.

At this point, I'd like to throw my 2 cents in as well. I also like to use basic text editors, although I am growing very fond of the NetBeans IDE. As you know, I also contribute patches and enhancements to JSch. In order to make the code more legible when I am working with it, I use jalopy. It was very easy for me to add to the existing build.xml, and the code comes out looking great in any editor. I simply made the following changes to the build.xml file:
diff -r1.3 build.xml
>   <property name="jalopy" location="jalopy"/>
>   <target name="jalopy" depends="compile">
>         <echo>${jalopy}</echo>
>     <taskdef
>       name="jalopy"
>       classname="de.hunsicker.jalopy.plugin.ant.AntPlugin"
>     >
>         <classpath>
>               <fileset dir="${jalopy}" includes="**/*.jar" />
>       </classpath>
>     </taskdef>
>     <jalopy
>       convention="${jalopy}/jalopy.xml"
>       loglevel="warn"
>       threads="2"
>     >
>         <fileset dir="${src}" includes="**/*.java" />
>     </jalopy>
>   </target>
<   <target name="dist" depends="compile"
>   <target name="dist" depends="jalopy"
I created a "jalopy" folder that holds the following files:
If you are interested, I would be happy to email these files to you directly, or send you the links for where to get these files directly.