sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: (Arnold D. Robbins)
Subject: Re: sam confused, Q: arrow keys
Date: Tue, 30 May 1995 10:00:00 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> I got sam a couple of days ago. I guess it's a nice thing. But I ran
> into two problems with it:
> 1) sometimes I end up in a situation when the whole editing menu
> (second mouse key) is displayed with parens around the topics and none
> of the commands typed into the ~sam~ window has any effect. I neither
> understand how I get into this situation nor how to escape from. All I
> can do is to terminate sam. Any help?

This is called a "protocol lock". There is a protocol between samterm,
which controls the display you interact with, and sam, which actually does
the editing. Occasionally, they get out of sync and there's nothing you
can do.

This usually happens to me after I've used the page-up or page-down keys and
then started typing before samterm has finished updating the screen. I can
usually switch to the sam window and send a 'w' and 'q' and then start a
new session.

Unfortunately, the Bell Labs guys can't seem to reproduce it... Sigh.

Arnold Robbins -- The Basement Computer		| Laundry increases
Internet: arnold@skeeve.ATL.GA.US		| exponentially in the
UUCP:	emory!skeeve!arnold			| number of children.
Bitnet:	Forget it. Get on a real network.	|    -- Miriam Robbins

      parent reply	other threads:[~1995-05-30 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
1995-05-29 15:43 ` Joerg Wittenberger
1995-05-30 13:29   ` hc05
1995-05-30 14:00   ` Arnold D. Robbins [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).