From: "Jason Spiro" <jasonspiro4@gmail.com>
To: help-gnu-emacs@gnu.org
Cc: kifer@cs.stonybrook.edu
Subject: need advice about fixing up my new vimpact-mode, a Vim emulation mode based on viper-mode
Date: Mon, 19 Feb 2007 05:37:51 -0500 [thread overview]
Message-ID: <c241693f0702190237s615bbef0p189b1b10516752cf@mail.gmail.com> (raw)
Hi help-gnu-emacs@gnu.org readers,
I have created a mode called vimpact-mode, a Vim emulation mode based
on viper-mode. It is based mainly on snippets of code from around the
Web. The pre-alpha is at:
http://www.jspiro.com/files/sw/vimpact-mode/vimpact-mode-0.0.1.el
I now have four questions.
Vimpact-mode is currently a major mode; that's bad. (It uses
define-derived-mode, which unfortunately lets me make major modes
only.) I want to make it into a minor mode, but I am not sure if I
should make it a derivative of viper-mode or if I should fork the
viper elisp files and distribute my mode's code.
Here are my design goals:
* I plan for all all viper and vimpact functions and customizable
variables to have the same prefix, "viper-". I don't want some to
begin with "viper-" and some to begin with "vimpact-". That'd be
confusing.
Question 1: Do you think I am right: is my way better than the other
option of having a mix of prefixes?
* I'd prefer vimpact to be an add-on to viper, not a fork of it, since
I want vimpact to contain only vim-derived features, not all-new ones.
Question 2: Do you think I am right about my add-on idea? Or would
it be better if all or most of the vimpact-mode changes could somehow
be merged into viper-mode (perhaps I could do it)?
Question 3: How much time would it take me, a mediocre elisp coder,
to make vimpact into a proper minor mode that starts up viper-mode
then adds the vimpact customizations (the add-on idea from before)?
How much time would it take me to merge the vimpact-mode changes into
the viper source code?
Question 4: Considering that I am an elisp newbie, is anyone willing
to do the work themselves? :-) You then would be the maintainer of
vimpact-mode.
Thanks in advance,
Jason Spiro
--
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
next reply other threads:[~2007-02-19 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 10:37 Jason Spiro [this message]
2007-02-19 15:49 ` need advice about fixing up my new vimpact-mode, a Vim emulation mode based on viper-mode Lennart Borgman (gmail)
2007-02-19 19:22 ` Jason Spiro
2007-02-19 21:59 ` Michael Kifer
2007-02-20 23:24 ` Jason Spiro
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=c241693f0702190237s615bbef0p189b1b10516752cf@mail.gmail.com \
--to=jasonspiro4@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kifer@cs.stonybrook.edu \
/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).