public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: David O'Shea <dcoshea@gmail.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: Applications in general; Emacs
Date: Wed, 14 Jun 2017 14:39:14 +0100	[thread overview]
Message-ID: <20170614143914.0705cd33@alans-desktop> (raw)
In-Reply-To: <CAN0DjM2Rsd492RCzFcthWa_Epg9KDzT0+jJmy9=LWj1HsaDKrA@mail.gmail.com>

On Wed, 14 Jun 2017 21:04:14 +0930
"David O'Shea" <dcoshea@gmail.com> wrote:

> On Wed, Jun 14, 2017 at 10:25 AM, Alan Cox <alan@llwyncelyn.cymru> wrote:
> >> Are there any applications for ELKS which aren't in the source tree,
> >> and is there a directory anywhere of applications for ELKS?  
> >
> > Lots of small apps will build fine. It's just another Unixalike after all.  
> 
> Oh yeah, it wouldn't be much fun if there wasn't any porting to do :)
> https://github.com/stangelandcl/ersatz-emacs/ wasn't too hard to get
> running, but it's a shame it doesn't recognize the enter key, I guess
> I will need to dig into some termcap stuff!

Nice. I think I need to see if I can get that to fit on FUZIX 8).

There are btw some goodl libraries of buffer management code. The Joe
editor has a very nice architecture for this although joe itself is too
big for a 16bit machine. Joe uses lists of gap buffers, allowing each gap
buffer to be moved to/from disk as needed.

For the enter key check the termios setup carefully and see if you are
getting \r and \n confused somewhere ?

Alan



  reply	other threads:[~2017-06-14 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  0:04 Applications in general; Emacs David O'Shea
2017-06-14  0:55 ` Alan Cox
2017-06-14 11:34   ` David O'Shea
2017-06-14 13:39     ` Alan Cox [this message]
2017-06-17 12:26       ` David O'Shea
2017-06-19 13:57         ` Alan Cox

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=20170614143914.0705cd33@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=dcoshea@gmail.com \
    --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