From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] When the sam command interpreter gets confused
Date: Fri, 17 Aug 2001 05:22:44 -0400 [thread overview]
Message-ID: <20010817092245.701.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Clint Olsen <clinton_olsen@yahoo.com> of "Fri, 17 Aug 2001 08:49:50 GMT." <1a8a5438.0108161309.4dd00444@posting.google.com>
Another cursor to mark the current output point might help. I too
sometimes miss the input point when trying to give it a command.
You have to type new input at the very end of the transcript. An easy
way to get there is to "send" something.
prev parent reply other threads:[~2001-08-17 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <clinton_olsen@yahoo.com>
2001-08-17 8:49 ` Clint Olsen
2001-08-17 9:22 ` Scott Schwartz [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:
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=20010817092245.701.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=9fans@cse.psu.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).