From: serge@euler.berkeley.edu serge@euler.berkeley.edu
Subject: Programmability
Date: Fri, 3 Jun 1994 18:13:43 -0400 [thread overview]
Message-ID: <19940603221343.neFxFTiMciAmphtwXvBBQ4UjosKibz_k-n4_Fnu2oB4@z> (raw)
Just out of curiosity, would anyone happen to know why programmability
was considered useful for a debugger (acid), but wasn't for an editor
(sam)? Perhaps if I could impose on the authors to comment on this?
(I'm not trying to start a flame war or anything of the sort, I would
simply like a better understanding of the issues at hand.) Thank you
very much.
reply other threads:[~1994-06-03 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19940603221343.neFxFTiMciAmphtwXvBBQ4UjosKibz_k-n4_Fnu2oB4@z \
--to=serge@euler.berkeley.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).