From: "Jason Spiro" <jasonspiro4@gmail.com>
To: "Michael Kifer" <kifer@cs.sunysb.edu>
Cc: jshawkin@eecs.umich.edu, spadgett1@nc.rr.com,
brad.beveridge@gmail.com, help-gnu-emacs@gnu.org,
Alessandro Piras <laynor@gmail.com>,
samuel.padgett@gte.net
Subject: Re: need advice about fixing up my new vimpact-mode, a Vim emulation mode based on viper-mode
Date: Tue, 20 Feb 2007 18:24:03 -0500 [thread overview]
Message-ID: <c241693f0702201524g42da175drbf8fa5087cbb5a53@mail.gmail.com> (raw)
In-Reply-To: <9011.1171922352@cs.sunysb.edu>
Hi Michael, thanks for replying.
A new development: After sending out this email, Alessandro mailed me
privately about his own vim emulation code. I will send it to you
privately and also to whoever wants. It is public domain license; I
hope to rename the code and post it on EmacsWiki.
But my questions below still apply :-)
2007/2/19, Michael Kifer <kifer@cs.sunysb.edu> wrote:
[snip]
> "Jason Spiro" <jasonspiro4@gmail.com> writes:
...
> > http://www.jspiro.com/files/sw/vimpact-mode/vimpact-mode-0.0.1.el
> ...
> I think it is not acceptable to use the same prefix as some other package
> unless your package can be logically considered an extension of that other
> package. Even then it might be better to use a different prefix.
Even though it can be confusing for users that a mode which is based
on another mode has 2 different prefixes? :-)
> Yes. In fact, why can't it be just another viper keymap?
Because I think users will contribute more changes if the official
source sits on the EmacsWiki. It's simply easier to make changes. And
easier to roll back bad changes. :-)
Emacs is cool in that it's the only app I know of where many plugins
are editable text sitting on a wiki.
> Eventually maybe. I haven't used vim extensively for a long time, but
> what kind of essential functionality are you planning to add?
A few examples:
* Point movement features, gg
* Scrolling features, zt zb zz
* Search for word features, * #
* Tags support, C-] and C-t
* Undo/redo, u C-r
* Window manipulation, C-wC-w, C-wo, C-wc
* Expand abbreviation, C-n
* Visual mode commands, v, o, O, d, y, c
* split, vsplit, bdelete, bn
> Here is an algorithm to measure the time:
>
> 1. Start by implementing exactly 1/2 of the vimpact-mode functionality.
> 2. Carefully measure the time it took you to do this.
> 3. Multiply that amount by 2 (that is number "two").
> 4. Add 20% to the result to cover various eventualities.
>
> :-)
haha
--
Jason Spiro: computer consulting with a smile.
I also provide training and spyware removal services for homes and businesses.
Call or email for a FREE 5-minute consultation. Satisfaction guaranteed.
+1 (416) 781-5938 / Email: info@jspiro.com / MSN: jasonspiro@hotmail.com
prev parent reply other threads:[~2007-02-20 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 10:37 need advice about fixing up my new vimpact-mode, a Vim emulation mode based on viper-mode Jason Spiro
2007-02-19 15:49 ` Lennart Borgman (gmail)
2007-02-19 19:22 ` Jason Spiro
2007-02-19 21:59 ` Michael Kifer
2007-02-20 23:24 ` Jason Spiro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c241693f0702201524g42da175drbf8fa5087cbb5a53@mail.gmail.com \
--to=jasonspiro4@gmail.com \
--cc=brad.beveridge@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jshawkin@eecs.umich.edu \
--cc=kifer@cs.sunysb.edu \
--cc=laynor@gmail.com \
--cc=samuel.padgett@gte.net \
--cc=spadgett1@nc.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).