From: Giles Hutton <hutton.giles@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] libframe Go port
Date: Sun, 11 Oct 2015 12:07:08 +0000 [thread overview]
Message-ID: <CANJh4-0W3JNim3B2UkUuW0kaJeLSUs0M8FA_ZS7HUqUmG2vW7Q@mail.gmail.com> (raw)
In-Reply-To: <20151011100748.GA23696@staven.pl>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Initially my main complaint was simply the heavy use of the mouse; it felt
jarring to have to move my hand off home row. However, I've now just
chalked that up to inexperience with acme.
Right now I actually can't think of anything I particularly miss about vim
text editing, which I guess is why I've dropped the idea.
On Sun, Oct 11, 2015 at 11:10 AM Staven <staven@staven.pl> wrote:
> On Sat, Oct 10, 2015 at 09:27:57PM +0000, Giles Hutton wrote:
> > better than vim, but acme's text editing was a bit too simplistic
> compared
> > to vim. So my initial intention was to port acme to Go, and add in
> vi-style
> > modal editing.
>
> What text editing features from vim do you miss in Acme?
>
>
>
[-- Attachment #2: Type: text/html, Size: 999 bytes --]
next prev parent reply other threads:[~2015-10-11 12:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 15:42 Giles Hutton
2015-10-10 17:00 ` Tharaneedharan Vilwanathan
2015-10-10 17:03 ` Siarhei Zirukin
2015-10-10 17:29 ` Skip Tavakkolian
2015-10-10 17:55 ` Kurt H Maier
2015-10-10 18:05 ` Skip Tavakkolian
2015-10-10 18:09 ` Skip Tavakkolian
2015-10-10 18:23 ` Kurt H Maier
2015-10-10 18:38 ` Skip Tavakkolian
2015-10-10 22:09 ` Kurt H Maier
2015-10-10 17:20 ` Skip Tavakkolian
2015-10-10 17:25 ` Tharaneedharan Vilwanathan
2015-10-10 20:55 ` Staven
2015-10-10 21:18 ` Tharaneedharan Vilwanathan
2015-10-10 21:27 ` Giles Hutton
2015-10-11 10:07 ` Staven
2015-10-11 12:07 ` Giles Hutton [this message]
2015-10-16 16:42 ` Bakul Shah
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=CANJh4-0W3JNim3B2UkUuW0kaJeLSUs0M8FA_ZS7HUqUmG2vW7Q@mail.gmail.com \
--to=hutton.giles@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).