[comp.windows.x] X11R4 public fixes #13 and #14 now available on expo get both

swick@EXPO.LCS.MIT.EDU (Ralph R. Swick) (07/19/90)

Patches for a variety of problems in Xt are now available via anonymous ftp
or the xstuff mail archive server on expo.lcs.mit.edu (18.30.0.212).  This is
a 2 volume set: make sure that you apply both fix 13 and 14 before rebuilding.

These patches fix the following problems:

    Make accelerator resources shareable
    Re-register key and button grabs when translation tables are modified
    Allow translation tables to include new-lines in action parameters
    Make XtAugmentTranslations really augment after fix #12
    Allow an input callback to be registered for more than one condition
    Allow both DebugLibXt and ProfileLibXt to be YES in site.def
    Include DESTDIR in the default for XFILESEARCHPATH
    Small reductions in memory usage
    Performance improvements in resource conversion cache lookup
    Configure windows and change XSetWMSizeHints in correct order for old wm's
    Keep geometry hints in WM_SIZE_HINTS updated for old wm's
    Fix some portability problems

Fixes are available via anonymous ftp to expo.lcs.mit.edu (18.30.0.212), in
the directory /pub/R4/fixes/, in files with prefix "fix-".  The latest fixes
are "fix-13" and "fix-14".  Fixes get put on expo in batches at intervals only.
Fixes usually propagate to other distribution sites as well, so it may pay
to check at a nearer site first.

For those without ftp access, individual fixes can be obtained by mail by
sending a message to xstuff@expo.lcs.mit.edu.  In the usual case, the
message should have a subject line and no body, or a single-line body and
no subject, in either case the line looking like:
	send fixes 13
(e.g. to get fix 13).  To get a summary of fixes, make the line:
	index fixes
If you need help, make the line:
	help
Some mailers produce mail headers that are unusable for extracting return
addresses.  If you use such a mailer, you won't get any response.  If you
happen to know an explicit path, you can include a line like
	path foo%bar.bitnet@mitvma.mit.edu
or
	path zot!gzork!me@uunet.uu.net
in the body of your message, and the daemon will use it.