From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: how to make it stop?
Date: Fri, 4 Dec 1992 01:43:41 -0500 [thread overview]
Message-ID: <92Dec4.014401est.2516@groucho.cs.psu.edu> (raw)
In lesser editors, like emacs, one can hit ^G to interrupt an operation
that is taking a long time. It turns out that sam takes a very long
time to process
,x v/^#//viewpoint/+-
on a buffer containing /etc/termcap, but there doesn't seem to be any
way to make it give up. The menus have stopped working, and ps says
it's blocked writing to a socket, so it's probably deadlocked. Sigh.
reply other threads:[~1992-12-04 6:44 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=92Dec4.014401est.2516@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.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).