From: "ozan s. yigit" <oz@nexus.yorku.ca>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: (click) undo
Date: Sun, 18 Sep 1994 23:37:22 -0400 [thread overview]
Message-ID: <94Sep18.233733edt.9224@nexus.yorku.ca> (raw)
indeed, i undo with some frequency, and a good portion of those undoes
are necessiated outside the sam window, which means going back and forth
between the sam window and the current window. i cannot however use my own
odd editing activities as a basis good design, and i also think that there
may be more than one design issue involved here. i still wonder what other
sam-fans think. what is the typical undo activity of an average sam user?
on a related topic: undo is also omitted from the protocol, which
of course reflects the needs of the current samterm. a more general
protocol would probably include it.
oz
next reply other threads:[~1994-09-19 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-09-19 3:37 ozan s. yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-09-19 8:31 Andrew Higham
1994-09-19 9:38 ` Gerry.Tomlinson
1994-09-19 8:27 Steve_Kilbane
1994-09-16 4:29 rob
1994-09-15 7:54 Ozan Yigit
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=94Sep18.233733edt.9224@nexus.yorku.ca \
--to=oz@nexus.yorku.ca \
--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).