From: hc05%beirnek@uunet.UU.NET (Beirne Konarski)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: I give up
Date: Thu, 4 Nov 1993 07:35:10 -0500 [thread overview]
Message-ID: <9311041235.AA17977@beirnek> (raw)
OK, I have been using SAM for a week now, trying to figure out why it
is a good editor to use. I am now giving up. The documentation
implies that it is better than vi(my favorite) or emacs, but I cannot
figure out why. Sure, it has a clever command language and it has not
internal limits, but it is hard to use for heavy-duty writing and
editing. It doesn't autoindent, and I need three hands to operate the
keyboard and the mouse. I can see using it in some special cases, like
when I need to work with a big file, but it makes no sense otherwise.
Is there something I am missing?
Beirne
--
-------------------------------------------------------------------------------
Beirne Konarski | Reading maketh a full man, conference a
beirnek@summitis.com | ready man, and writing an exact man.
"Untouched by Scandal" | -- Francis Bacon
-------------------------------------------------------------------------------
next reply other threads:[~1993-11-04 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-11-04 12:35 Beirne Konarski [this message]
1993-11-04 15:58 pete
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=9311041235.AA17977@beirnek \
--to=hc05%beirnek@uunet.uu.net \
--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).