sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: steve@gec-epl.co.uk (Steve_Kilbane)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam + ptys, anyone?
Date: Mon, 24 Jan 1994 11:41:24 -0500	[thread overview]
Message-ID: <9401241641.AA13692@cuthbert.sdd> (raw)

i've often wondered about this, but the 'emacs-ism' of it all has put me
off. plus, of course, it would complicate sam no end, i suspect. i think
a better way to do it would be to just get Help (or whatever rob's latest
GUI was). Kind of layer shell, terminal driver, editor, window system and
sam system, so that it takes the capability into account, rather than it
being kludged in.

Of course, if you can do it in a 10-line patch, i'll use it. :-)

steve


             reply	other threads:[~1994-01-24 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-01-24 16:41 Steve_Kilbane [this message]
1994-01-24 17:14 ` Peter Huang
  -- strict thread matches above, loose matches on Subject: below --
1994-01-24 14:37 Arnold Robbins

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=9401241641.AA13692@cuthbert.sdd \
    --to=steve@gec-epl.co.uk \
    --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).