From: "Ozan S. Yigit" <oz@sis.yorku.ca>
To: rob@research.att.com
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: changes not in sequence
Date: Wed, 26 May 1993 16:18:37 -0400 [thread overview]
Message-ID: <9305262018.AA13783@sis.yorku.ca> (raw)
In-Reply-To: Your message of "Tue, 25 May 93 23:48:47 EDT." <93May25.234919edt.2714@hawkwind.utcs.toronto.edu>
> i have a whole new system now that contains much more efficient code
> to do all this stuff, obviating the need for the extra level of cache
> and hence making it possible to sort the changes (as in fact i do in
> this new system). the code could be retrofitted but it's a huge job ...
are there any other improvements in the new system we can borrow for
sam? the message protocol between the term and the editor proper? any
new commands and/or interface ideas?
oz
next prev parent reply other threads:[~1993-05-26 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-26 3:48 rob
1993-05-26 20:18 ` Ozan S. Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-24 20:30 Ronnie Mainieri
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=9305262018.AA13783@sis.yorku.ca \
--to=oz@sis.yorku.ca \
--cc=rob@research.att.com \
--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).