* Note the ugly hack of adding "foo~" for every "foo" suffix.
* Note also that when "*.*" is in the glob list all files should be
available but it looks like this isn't working yet for some reason.
patterns instead of one pattern per suffix. (This was almost never
used -- only when saving a file that is in text mode.)
* Since this default is the same that the scheme
mode ("framework/private/scheme.rkt") sets, remove that
setting. (Leave it commented in case there's need to have some
different global default.) It makes the above default get used when
saving a scheme-mode file.
* Finally, for some reason the code in "framework/private/finder.rkt"
was not using these `default-filters' at all for the file open dialog
in `*get-file'. (I tracked it back to CVS when the code was written,
and it was never used.)
I made it use it now. This is visible on gtk (and probably on
windows, not sure what OSX does) in that openning a file would show
you all files. After this change, it would show only racket source
files, but there will be an option to switch the pattern to show all files.
** If the previous setup (showing all files) was intentional, it would
be better to simply change "drracket/private/main.rkt" to add the
racket source globs before the default. In that case it might also
make sense to uncomment the change in scheme.rkt back in, so when
saving the default is the racket file suffixes (but this sounds
like a confusing UI).
See in-code comments for how this is just a rough feature to be used if
needed (and improved when it becomes necessary). That can just as well
go to the FIXME of using a string constant.
* Add captcha url (unused, yet)
* The second argument to `call/input-url' can be a one-argument function
since the call doesn't send it any headers.
Still needs to be done: check the HTTP response for an error status, and
make it fail as a result (currently it just assumes that any response is
fine, which can change in case of a captcha failure). Then, add a
captcha challenge if one is found, otherwise ignore.
because the previous documentation didn't actually define the form;
the examples were good, but epecting a reader to infer meaning
from examples wasn't good enough. The use of a `module-path?' contract
in the old docs wasn't appropriate; contracts apply to values, while
grammar productions should be used to document syntax constraints.
Also, `module-path?' was too permissive (only literal strings and
identifiers are actually allowed), while the actual syntax allows
either a single path or a sequence.
