The following expression would trigger an arity error:
(subst-all
(make-simple-substitution (list 'a 'z) (list (-val 3) (-val 5)))
(make-ListDots (make-F 'z) 'a))
Having `__VFP_FP__` defined does not mean that VFP instructions are
available; it just means that floating-point is native-endian.
According to
https://wiki.debian.org/ArmEabiPort
the absence of `__SOFTFP__` combined with the precense of `__VFP_FP__`
can mean VFP, though.
This rule supplements the old (but now less applicable) rule to
never add debugging-compiled files in the main installation's
"collects" directory.
Note that the new rule does not prevent compilation in
main-distribution packages that are linked, as in the development mode
set up by `make' in the Racet repository's top-level directory.
I think that's probably ok, since the intent of the check is mainly
just to not write to shared installation spaces, which shouldn't be
an issue for development mode.
- 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.
