Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!tektronix.tek.COM!toddb%tekcrl.CRL
From: toddb%tekcrl.CRL@tektronix.tek.COM (Todd Brunhoff)
Newsgroups: comp.windows.x
Subject: Re: xmodmap
Message-ID: <8805041846.AA15629@tekcrl.CRL.TEK.COM>
Date: 4 May 88 18:46:45 GMT
References: <8805031857.AA04904@janeb.cs.wisc.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 37

>> What does "sequence lost" mean?

It actually has nothing to do with the xmodmap program or the hardware
you are running on.  It is a message from an internal xlib routine
that tries to interpolate a 32 bit sequence number from the least significant
16 bits that are provided in all protocol events, replies and errors.
What it means is that Xlib thought the sequence number was marching
along quite nicely:

	0x3f01, 0x3f02... 0xfffe, 0xffff, 0x10000, 0x10001

and all of a sudden, before it could adjust its suspenders, it
looked as if the number went backwards!  Oh no!  What it suggests is
that there is a problem in Xlib, the server or your compiler.
Its also particularly interesting because a program like xmodmap
would not be generating enough requests to get the number up
high enough to overflow into the next 16 bits, like the sequence
shown above, which is where this problem usually showed up when
it was first written.

I'm afraid it doesn't happen on my machine so I bet its your compiler.
Can anyone else repeat this using xmodmap on the file

	remove Lock = Caps_Lock
	remove Control = Control_L
	keysym Control_L = Caps_Lock
	keysym Caps_Lock = Control_L
	add Lock = Caps_Lock
	add Control = Control_L
	keysym BackSpace = quoteleft asciitilde
	keysym quoteleft = Escape

---------------
Usenet:       {ucbvax,decvax,allegra,uw-beaver,hplabs}!tektronix!crl!toddb
{CS,ARPA}net: toddb%crl.tek.csnet@relay.cs.net                       c--Q Q
US:           Todd Brunhoff; Visual Systems Lab; Tektronix, Inc.         `
              Box 500  MS 50-662, Beaverton OR 97077                     -
Phone:        (503) 627-1121