From: Matthew Hannigan <mlh@zip.com.au>
To: 9fans@cse.psu.edu
Subject: sam video? (Re: [9fans] Re: User Interface)
Date: Sun, 26 Aug 2001 10:58:33 +0200 [thread overview]
Message-ID: <3B88BA39.6FA3B67B@zip.com.au> (raw)
In-Reply-To: <20010824134555.4D8A2199D7@mail.cse.psu.edu>
rob pike wrote:
>
> I'm confused. Our copy of vi doesn't have a ~ command.
Maybe it's my fault. I mentioned that "other editor".
I was merely pointing it's lack of user feedback and
making an analogy with sam, which simiarly is low
on user feedback. At least for a newbie on first startup.
I also think that typically things like sam are
demonstrated to others and not picked up cold from manuals.
For those of us who are making the leap alone it
would be tremendously useful to see a little video
or animated movie.
Care to make one?
Regards,
-Matt
ps. promise i won't mention that other editor again.
prev parent reply other threads:[~2001-08-26 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 13:45 [9fans] Re: User Interface rob pike
2001-08-24 14:19 ` Dan Cross
2001-08-26 8:58 ` Matthew Hannigan [this message]
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=3B88BA39.6FA3B67B@zip.com.au \
--to=mlh@zip.com.au \
--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).