Ville Mattila
1/27/2005 5:15:00 PM
I have had opportunity to be a beta tester for this release.
Guys this is some fantastic piece of work that Lothar is doing!!
Don't be phobic and try arachno!
I appended some comments about added features.
Lothar Scholz <mailinglists@scriptolutions.com> writes:
> Control-D Control-M (Mnemonic: Display-Matching) shows matching 'end' lines and
>
This great helper when you got those annoyning parse errors in your
code.
It first looks bit confusing, but in a second glance you are
starting see, where the bug is. When I showed this one to my
collague, he said that he will finally install arachno and starts
to use it instead of Eclipse.
>
> Auto de-indentation is triggered immediately after you typed the end/else/elsif/rescue
> keyword.
The auto identation works as well in emacs even better in some cases.
This way better than in eclipse.
>
> Debugger now works with the official 1.8.1 and 1.8.2 release
>
> Debugger works with RubyGems version 1.8.4
> Single stepping into a "require" gives strange results, so place a breakpoint behind the
> require statement and then do a continue (F9 key)
Arachno's debugger is very good and fast!
>
>
> Control-Space gives a context based completition.
> Tokens are generated from the content of the current file (excluding comments, regexpr
> and strings) and then presented in a list. Tokens are ordered by there distance from the
> current caret line. You can use Control-Space or the cursor keys to move between different choices.
This feature is absoute treasure. It saves typing about 80%. Try it out.
This feature is worth trying alone.
>
> Code-Folding:
> This feature is based on the same syntax parser that is used for the navigation sidebar.
> It collapses methods, classes and modules. Folding also collapses the comment above an entity,
> leaving the first comment line visible which should contain a summary of the method/class/module.
>
Code folding works great!
> Indentation Lines:
> Arachnos identation lines are not tab lines as they are in scintilla.
> They are based on existing indentations, independent if the line is adjusted on a
> tab position.
These lines are great help as well for helping understanding where parse
error might be!