From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Does sam accepts interrupt signal
Date: Thu, 27 Mar 2008 15:46:28 +0000 [thread overview]
Message-ID: <7cd16d3520771383ac18191fb98fbd23@terzarima.net> (raw)
In-Reply-To: <b954b2060803270812p63863829q23edbf036afbbf8e@mail.gmail.com>
it has been some time since i last used sam interactively,
but your description
sam appears to forget the state (in fact it's I that forget
it) and treat my input as plain text. In this case, no matter putting
a single dot or completing with a `/' could not save me. As a result,
sounds as though you've ended up typing behind the point where sam
is actually reading input (ie, in the transcript).
try snarfing and sending a newline (or perhaps a .) to resynchronise.
next prev parent reply other threads:[~2008-03-27 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 15:12 Hongzheng Wang
2008-03-27 15:46 ` Charles Forsyth [this message]
2008-03-29 5:03 ` Hongzheng Wang
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=7cd16d3520771383ac18191fb98fbd23@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.net \
/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).