| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It defaults to "-Q" but users can instead use "-q", which is useful
if "site-start.el" contains essential settings. Also rename `BATCH'
to `EMACS_BATCH', add `EMACS_ORG' and `EMACS_INTR', and rework use
of related variables.
|
|
And rename PKGSTEXI to just PKGS.
|
|
We now use the implementations from the Cond-Let package.
|
|
Re magit/magit#5472.
|
|
|
|
|
|
Closes #5429.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+73853.
|
|
|
|
- Files are not the only inputs to `texi', so we cannot rely on their
modification times alone, to determine whether a rebuild is required.
The new `redo-docs' always regenerates the texi file and thus all
other formats. Use that target before publishing the manual.
- Teach `html-dir' to only regenerate if a texi file has actually been
touched.
- However when `html-dir' does regenerate, we must first remove all
existing html files, to avoid files that used to be generated but
are not being generated anymore, from sticking around.
|
|
|
|
|
|
That means that every commit starting with release N, that isn't part of
a later release, will claim to actually be release N. That is wrong for
every commit but N itself, but I was unable to get anybody else to care.
|
|
|
|
This is just a proof-of-concept. Until that changes its dead weight
that should not be packaged. Removing it from version control is the
only way to prevent it from getting packaged anyway.
|
|
|
|
|
|
`seq' isn't available from Melpa.
|
|
We are not doing that currently and haven't been for a while.
Should we ever start doing it again, we can just revert this;
no need to keep it around while we don't.
|
|
|
|
|
|
|
|
In Emacs 30 the advertised signature of `derived-mode-p' was changed
from (&rest modes) to (modes). The old calling convention is still
supported, and until everyone has updated to the yet to be released
Emacs 30.1, we have no choice but to keep using that.
|
|
|
|
|
|
Going forward I plan to deprecate things in place, and if
that doesn't work out, we can always revert this commit.
|
|
|
|
|
|
|
|
|
|
All my other Makefiles already used that variable
and the shared CI workflows expect that it is used.
|
|
This isn't used by make, but is needed for the Compile ci workflow.
|
|
Closes #4844.
|
|
|
|
Bump version/snapshot to make sure we get a Compat version
that includes the new macro. This had to be done manually
as the bump-snapshots make target suffers from bit rot.
Closes #4836.
|
|
|
|
Re #4669.
|
|
|
|
I've been doing that for a long time for many of my other packages
and nobody reported an issue, but if someone is trying to build magit
by running make in a terminal running inside emacs and that uses bash
4.3 or older, then that would fail now. On the other hand more people
likely try "EMACS=emacs-26.1 make" and then wonder why that doesn't
work. (The new variable for indicating to a shell that it is running
inside emacs is INSIDE_EMACS.)
|
|
|
|
Now that the code that was used to support magit-mode-derived modes
has mostly evaporated, it is okay to spread the little code that is
necessary to support other modes across the respective files.
|
|
It hasn't been true for quite some time that this library only (or
even just mostly) defined things that have "very little to do with
Git or Magit", and it is time to account for that.
"magit-base.el" serves a role similar to that of "magit-core.el",
except that it comes even earlier in the dependency tree. For that
reason other libraries that depend on one or more of the libraries
that `magit-base' depends on should just require that feature.
|
