From: Castor Fu <castor@drizzle.Stanford.EDU>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: sam or tk bug?
Date: Wed, 8 Mar 1995 12:30:40 -0500 [thread overview]
Message-ID: <199503081730.JAA18686@drizzle.Stanford.EDU> (raw)
I've started using sam on RS 6000's recently and have been getting
the following error relatively often (3 times in the past two days):
Xlib: sequence lost (0x10006 > 0xfcb) in reply type 0x0!
X Error of failed request: 0
Major opcode of failed request: 0 ()
Serial number of failed request: 6
Current serial number in output stream: 4043
Then samterm exits. Has anyone seen this before?
I think this might be connected with a Tk tool which I hacked together.
It provides some of the functionality of emacs's M-x compile, by
searching the results of a 'make' for errors, and sending in sam
commands through the named pipe. It also has hooks for the AT&T Toolchest
'cscope' program, to provide source browsing capability.
To make it more useful, it would be nice to have easier X selection
features in 'sam'. I think there were some chording patches a while back.
Maybe those would be most appropriate? I guess I'll have to dig through the
archives.
-castor
next reply other threads:[~1995-03-08 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-08 17:30 Castor Fu [this message]
1995-03-08 18:21 ` DaviD W. Sanderson
1995-03-08 19:12 hc05
1995-03-09 0:50 ` Michael F. Ledwidge
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=199503081730.JAA18686@drizzle.Stanford.EDU \
--to=castor@drizzle.stanford.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).