- paren color from brown to a neon blue
- string and number constants from green to a bright purple
- lighten the comment color
the basic problem is to try to keep the red error color very distinct
from the others and try to keep the others distinct from each other
(but that's less important)
Besides changing the URL scheme, the tag or branch is optional and
specified as a fragment (inspired by npm). Also, any subpath is expressed
as a "path=..." query (which similarly avoids giving a different meaning
to URLs than `git' itself would). The repository name can have a ".git"
suffix.
The "github://..." format is still supported for compatibility, but
`--type github' adds "git://..." instead of "github://..." if
neither is already present (which is incompatible, since branches
and tags are handled differently for the two forms).
Closes PR 13656
(See the PR for a discussion and my rationale for this choice.)
This change solves a long-standing problem with using @nonterm{}
inside @tt{} or other constructors that change the font, where
the font would be different (and uglier) than uses outside of font
changes.
Use better labels, such as "Available from Catalog" instead of "By List"
or "Do What I Mean" instead of "By Source".
Add filter box to the "Currently Installed" panel, andmake status marker
the same as on "Available from Catalog".
It's possible that an installation will have a package X already and
a user wants to install a different X. To make it all work out,
the user may have to also install a new Y for every installation-scoped
Y that refers to X --- maybe not easy, but at least possible as
a last resort.
This option makes install and update even more consistent, also
`--auto` still implies `--update-deps` only in update mode.
Make `--update-deps' consult the user in `search-ask' mode,
make it ignored in `fail' or `force' mode.
relative to some default settings instead of saving
the actual values
so changes to the default imply changes to everyone's actual
values for the prefs
closes PR 13810
This reverts commit de230bc1ef.
Now that path computatons are built in, and now that the sandbox allows
reading the configuration file, using the installation name doesn't
break with sandboxing.
The computations already existed in the built-in code, so moving
the functions reduces code duplication. Caching the values will
save a little time, but mostly it will avoid sandbox interactions
with the task of locating the main "collects" and "etc" directories.
Needs to do it when the relevant stderr is in effect.
Fixes PR 13744, except that something like this is still bad:
(with-output-to-file "/tmp/foo" #:exists 'append
(lambda ()
(parameterize ([current-error-port (current-output-port)])
(/ 1 0))))
But I think that it's a bad idea for the error display handler to be
called with the locally set port -- described in PR 13974.
