Heh. I've been threatening to write yet another
vi clone for quite some time now (I think the world needs an editor called evil), but
every time I start I'm reminded that pretty much everything
I want to do, vim already does.... More power to
you, though.
Favourite features (in vim):
- Very quick movement around files. This is the
biggest feature I can think of. Since I work with code
all day, using an editor that doesn't get in my way and
lets me jump around the file damn quick is really important
to me. This includes ctags, by the way.
- Perl hooks. 'Nuff said.
- Regex search/replace.
- General programming features, like syntax colouring and
bracket matching. I like vim's indent and comment
options, but the syntax is a bit hirsute.
Most Wanted features (for vim):
- Perl-style regexes. Switching context from Perl regex
style to vi regex style is really hard on my poor
widdle brain.
- Regex-based comment/indent/syntax hilighting. I
haven't looked too closely at vim 6's language
files, so this may have been solved.
- Faster, smaller, fewer bugs, you know the drill.
--
:wq
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
