From: "bob flandrena" <bobf@plan9.bell-labs.com>
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Tue, 25 Jun 1996 12:21:17 -0400 [thread overview]
Message-ID: <96Jun25.124309edt.24393@hawkwind.utcs.utoronto.ca> (raw)
> samterm seems to respond fairly badly to an input of {}
> if it has no files open.
i posted a fix to this several months ago:
% diff /n/dump/1995/0401/sys/src/cmd/sam/xec.c xec.c
29c29
< !utfrune("bBnqUXY!{", cp->cmdc) &&
---
> !utfrune("bBnqUXY!", cp->cmdc) &&
33c33
< if(cmdtab[i].defaddr != aNo){
---
> if(i >= 0 && cmdtab[i].defaddr != aNo){
there are several other bug patches for sam in
the boddle package available by anonymous
ftp at plan9.att.com in plan9/update/cmd/sam/829146783.rc.
the diff's are relative to the plan 9 version of
sam and require rc to unpack, but are easy to
extract by hand and apply to the unix version.
reply other threads:[~1996-06-25 16:43 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=96Jun25.124309edt.24393@hawkwind.utcs.utoronto.ca \
--to=bobf@plan9.bell-labs.com \
--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).