remove the "dock/undock test report" menu items from the show menu
(there are buttons in the window and this isn't really a show menu
type of thing)
Add support to the show menu item to make ordering the items
simpler.

Use that support to adjust the Show menu to have a better
ordering for the built-in DrRacket items.
fix sizing bug in tooltip windows
added a tooltip for set!'d variables
adjust the contract obligation aspect of check syntax
so that it uses tooltips instead of the modes

(so hopefully now people will actually see it ...)
removed the check syntax mode support
add a View menu item for the optimization coach
revert use of `lazy-require' in `racket/match' implementation

Using `lazy-require' under `begin-for-syntax' expands to a use of
`define-runtime-path' under `begin'for-syntax'. Unfortunately,
`define-runtime-path' doesn't yet work with `raco exe' when it
appears under `begin-for-syntax'. Although `define-runtime-path'
should be fixed, it may take a while. Meanwhile, reverting the
change allows programs that require `racket/gui/base' to work
with `raco exe'.

There's another `lazy-require' under `begin-for-syntax' that
doesn't seem to cause the same trouble, though.
fix related to recent module-resolver change
Post-release version for the v5.3 release
bring the language test up to date with the latest error messages

include in the release branch, please
adjusted the repl test suite for the new error messages
and the change to the racket/gui load-handler

(unfortunately, there is still another problem that keeps
the test suite from passing)

please merge to the release branch
module lang test now up to date with error message changes

please include in release branch
New Racket version 5.3.0.16.
typo
racket/gui/init: fix load handler
Add missing meta information for the new "future-visualizer" collection.
Make it possible to use "~" or "~user" in the installer.

I've looked for a while, and it seems that there is no easy way to do
this, not even in bash, and worse with /bin/sh.  So this is kind of
resorting to a simple parsing of the input, and using `eval' if it
starts with a tilde.  Note the hack of not doing that when there is a
space, otherwise the `eval' thing will silently ignore it.

This hack means that it's easy to get into a mess if quotes are used
after a tilde, but that was already the case with the use of `eval' to
handle environment variables.  It's not a real security issue, however,
since we're talking about a user who can just run any command anyway.

Also including a test file for the expansion functionality.  If anyone
wants to improve this code, making the tests pass would reveal the
tricky issues.

[FWIW, I've asked on the #bash channel, and the only serious suggestion
was getting the paths as command-line arguments.  This will, however,
defeat the point of being newbie friendly...]

Closes PR 12893.
Disable the `#:before-first' and `#:after-last' functionality in `add-between'.

Leave it working in splicing mode.  I prefer doing that over always
splicing them, since that would make a less uniform interface, so I
rather keep all options open.  There is no longer a `#:nothing' keyword,
which is the main point of this downgrade.

(See mailing list discussion on "no-argument" for the reason.)
Fix typo from commit 12a4ee8.