From: Miguel Bolanos <mike@linuxlabs.com>
To: Albrecht Kleine <kleine@ak.sax.de>
Cc: linux-8086@vger.kernel.org
Subject: Re: *vi*->e3
Date: Fri, 04 Jun 2004 20:41:39 -0600 [thread overview]
Message-ID: <1086403299.3221.8.camel@talena.hsol.net> (raw)
In-Reply-To: <200406041745.i54HjXOu008988@ak.sax.de>
[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]
Greetings.
On Fri, 2004-06-04 at 11:45, Albrecht Kleine wrote:
> Hi,
>
> > On Thu, 2004-06-03 at 12:51, Tommy McCabe wrote:
> > > I propose we replace the umpteen vi versions in
> > > elkscmd with e3, which has already been ported, is
> > > smaller and lighter, and has five different
> > > keybindings (yes, including vi's and emacs's). The
> > > main website: http://www.sax.de/~adlibit/ (Yes, it's
> > > written in English). The attachment is the ELKS
> > > version of e3 plus Makefile. It is written in assembly
> > > and requires nasm to build.
>
> > I'm not very sure about this... we could include it, but replacing vi..
> > i honestly would like to hear others opinions before moving forward with
> > this.
>
> My name is Albrecht Kleine, the author of e3.
> I would suggest to ship the ELKS version e3 additionally,
> but not replacing vi.
Oh... hehe nice to Meet you Albrecht :), its nice to see you reading
this list :)
>
> The reason is as follows: the elks port does _NOT_ include
> vi's and emacs's key bindings, but 'wordstar' in a fullscreen way.
>
So its decided.. we won't replace vi, but yes we will port e3 :)
> This stuff was forked in an early stage from e3/Linux
> into 16 bit for ELKS and DOS. Later I did not continue,
> because I never got much feedback. any my only reason to do
> this port was only to play with ELKS on an old 8086 PC.
>
Well elks have been certainly progressing a lot lately after a very long
period of inactivity, so you can be sure that feedback will come,
specially now that we will include e3 :)
> OTOH, it is really nice to read you considering
> to include e3 into elks_cmd, so that would be a reason
> to later improve this 16 bit stuff.
>
Good. We really hope that you can continue ur work on 16bit too, as it
will of great benefit for elks.
[...]
best wishes
Mike
--
--------------------miguel bolanos, systems administrator, linuxlabs
... ........ ..... .... 230 peachtree st nw ste 2701
the original linux labs atlanta.ga.us 30303
-since 1995 http://www.linuxlabs.com
office 404.577.7747 fax 404.577.7743
--------------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-05 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 18:51 *vi*->e3 Tommy McCabe
2004-06-04 15:25 ` *vi*->e3 Miguel Bolanos
2004-06-04 17:37 ` *vi*->e3 Jody
2004-06-04 20:32 ` *vi*->e3 Tommy McCabe
2004-06-04 17:45 ` *vi*->e3 Albrecht Kleine
2004-06-05 2:41 ` Miguel Bolanos [this message]
2004-06-09 13:42 ` *vi*->e3 Miguel Bolanos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1086403299.3221.8.camel@talena.hsol.net \
--to=mike@linuxlabs.com \
--cc=kleine@ak.sax.de \
--cc=linux-8086@vger.kernel.org \
/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