[4791] in Athena Bugs
Re: xmh fails on edit operation
daemon@ATHENA.MIT.EDU (Ralph R. Swick)
Thu Apr 19 08:48:49 1990
To: geer@crl.dec.com
Cc: bugs@crl.dec.com, bugs@ATHENA.MIT.EDU, xbugs@expo.lcs.mit.edu
In-Reply-To: Your message of Wed, 18 Apr 90 21:24:38 -0400.
Date: Thu, 19 Apr 90 08:48:25 EDT
From: Ralph R. Swick <swick@ATHENA.MIT.EDU>
Cut via ^W from a large message (177k bytes) results
in the following:
X Error of failed request: BadLength (poly request too large
or internal Xlib length error)
Major opcode of failed request: 18 (X_ChangeProperty)
Minor opcode of failed request: 0
Resource id in failed request: 0x8000a5
Serial number of failed request: 73951
Current serial number in output stream: 73977
The bug actually lies in the Text widget; it should recognize
the (dynamic) server limit on maximum property size and attempt
to handle errors. This could be handled statically with an
additional resource (e.g. XtNmaximumCutBufferSize) or dynamically
with an error popup on failure.
As a work-around if you want to do this frequently, you can modify
the Text widget translations so that it doesn't try to store the cut
into the properties used by Andrew&oldemacs (i.e. CUT_BUFFERn):
*Text.translations: #override \n\
<Btn1Up>: extend-end(PRIMARY) \n\
<Btn3Up>: extend-end(PRIMARY) \
(compared to the default which is
<Btn1Up>: extend-end(PRIMARY, CUT_BUFFER0)
<Btn3Up>: extend-end(PRIMARY, CUT_BUFFER0)
)
-R.
