sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: mike@skinner.cs.uoregon.edu, sam-fans@hawkwind.utcs.toronto.edu
Date: Mon, 12 Apr 1993 20:32:37 -0400	[thread overview]
Message-ID: <9304130032.AA01842@netapp.netapp.com> (raw)

This doesn't work if you compulsively write out dirty files in the
middle of an edit session. (I don't think I'm the only one who does
this.)

What's the real problem? That sam doesn't start up fast enough for
a true synchonous edit? I have my sam dimensions and coordinates
predefined so that a new sam pops up in the same location every
time. The only problem I have is that a new sam takes too long
to start up. I suspect this is partly sam's design (2 processes
need to run instead of 1) and general Unix and X11 bloat.

In general I don't use B because I want to associate a particular
directory with each instance of sam. Ideally sam would just take
over the terminal window in which it is invoked, but I think it
would take a different window system for that to happen.


                 reply	other threads:[~1993-04-13  0:40 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=9304130032.AA01842@netapp.netapp.com \
    --to=byron@netapp.com \
    --cc=mike@skinner.cs.uoregon.edu \
    --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).