From: noel@es.su.oz.au
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: Newbie Question about Sam, and keyboard operations
Date: Sat, 8 Jan 1994 18:13:24 -0500 [thread overview]
Message-ID: <199401091013.16023.out.babab@es.su.oz.au> (raw)
In-Reply-To: <9401072302.AA24306@ghoti.netapp.com>
From: byron@ghoti.netapp.com (Byron Rakitzis)
Subject: Re: Newbie Question about Sam, and keyboard operations
>yes, there is a way to perform cursor movement without using the mouse.
>use emacs.
Ha ha, very funny.
It's intolerant sarcasm like this that makes labs religion so much fun,
eh?
i am afraid that the earlier correspondent has failed to see something
very basic in the design of sam. if my chiding takes the form of sarcasm,
that hardly amounts to intolerance.
next prev parent reply other threads:[~1994-01-08 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-01-07 23:02 Byron Rakitzis
1994-01-08 23:13 ` noel [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-01-07 16:15 Mark C. Carroll
1994-01-07 22:31 ` noel
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=199401091013.16023.out.babab@es.su.oz.au \
--to=noel@es.su.oz.au \
--cc=sam-fans@hawkwind.utcs.toronto.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).