From: forsyth@minster.york.ac.uk
To: sam-fans@hawkwind.utcs.utoronto.ca
Subject: teaching novices to use sam
Date: Wed, 4 Aug 1993 14:15:35 -0400 [thread overview]
Message-ID: <swordfish.744490851@minster.york.ac.uk> (raw)
if they like its style, it's fairly easy to get experienced
programmers to use sam happily. has anyone, perhaps at a university,
any experience in trying to get novices (ie, students) to use
sam as a first editor? (some, but not all, will actually have used
fairly simple minded editors under Windows and similar systems
at home and at school.) i made sam and a few other mouse-based
editors available to students during the last academic year,
but because many were taught vi (not by me) as the first editor,
i suspect they never bothered to switch. others found difficulty
getting to grips with the mouse (quite likely because it wasn't
a good make of mouse). what experiences have others had/seen?
next reply other threads:[~1993-08-04 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-08-04 18:15 forsyth [this message]
1993-08-06 0:59 ` John Mackin
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=swordfish.744490851@minster.york.ac.uk \
--to=forsyth@minster.york.ac.uk \
--cc=sam-fans@hawkwind.utcs.utoronto.ca \
/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).