9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text editor
Date: Fri, 26 Apr 2002 10:52:49 -0400	[thread overview]
Message-ID: <20020426145434.68DA319A2D@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

i've used Wily for quite a bit (although not for a good while now)
and found the differences and inconsistancies to be really painful.
i imagine it'd still be a good step up for someone not already
familiar with acme. the acme-in-inferno-on-unix solution is one
i use occasionally now (since i'm only occasionally at a unix box)
and really like.

since my unix boxes are generally remote, i edit files on them most
of the time by 9fs'ing (using u9fs on the unix box) and running
acme. occasionally i have to edit files on a box i don't admin (and
thus can't put u9fs on), and sam -r works well for that. even that's
somewhat awkward (to be polite) now... i _really_ miss acme's
mouse chording.
ア


[-- Attachment #2: Type: message/rfc822, Size: 1422 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text editor
Date: Fri, 26 Apr 2002 10:10:00 -0400
Message-ID: <7982c19b270270becaf0164e247d55f8@plan9.bell-labs.com>

> To each his own.  As I've said, I'm comfortable with vi on Unix boxen
> and with sam on Plan 9.  Your mileage may vary.  There are situations

i advise you, and anyone else in your situation, not to try acme.
once you get used to it you'll curse vi and never be able to get
anything done on unix.

             reply	other threads:[~2002-04-26 14:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 14:52 anothy [this message]
2002-04-26 16:59 ` peter huang
  -- strict thread matches above, loose matches on Subject: below --
2002-04-29  9:36 Andrew Simmons
2002-04-26 17:31 Russ Cox
2002-04-26 14:10 Russ Cox
2002-04-26 10:27 ` Sam Hopkins
2002-04-29  9:40 ` Douglas A. Gwyn
2002-04-26 13:40 forsyth
2002-04-26 13:27 presotto
2002-04-26 12:46 bwc
2002-04-26 16:33 ` mcguire
2002-04-30  1:54   ` chad
2002-04-26 12:40 nigel
2002-04-26 11:41 forsyth
2002-04-26 11:39 rog
2002-04-26 11:45 ` Boyd Roberts
2002-04-26 10:45 nigel
2002-04-26 11:04 ` Alexander Viro
2002-04-26 10:22 nigel
2002-04-26 11:15 ` Boyd Roberts
2002-04-26 11:25   ` Boyd Roberts
2002-04-26 16:06   ` Ronald G Minnich
2002-04-26 10:11 rog
2002-04-26 23:30 ` Micah Stetson
2002-04-26  9:49 nigel
2002-04-26 10:21 ` Alexander Viro
2002-04-26 11:38   ` Michael Grunditz
2002-04-26 20:35   ` Dan Cross
2002-04-29  9:40     ` Douglas A. Gwyn
2002-04-29  9:36 ` Andrew Stitt
2002-04-29 15:58   ` Douglas A. Gwyn
2002-04-26  8:47 Andrew Stitt

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=20020426145434.68DA319A2D@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --cc=9fans@cse.psu.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 NNTP newsgroup(s).