Age | Commit message (Collapse) | Author |
|
I'm not sure if containerized can be used as a field too, but I only
see it used as a top-level command in the examples.
|
|
26.1 was released in 2018 and is in the current Debian oldstable
(Buster). I'm unlikely to build an older Emacs version than that in
order to investigate and work around any incompatibilities that are
reported, so mark it as the minimum.
Message-Id: <20220222043213.218747-1-kyle@kyleam.com>
|
|
cl-lib was added in the Emacs 24.3 release, so cl-lib no longer needed
to be specified when ca4d60d (Change Emacs requirement for Emacs 24 to
Emacs 24.5, 2018-08-16) changed (emacs "24") to (emacs "24.5").
|
|
--cores has been a mandatory argument since v5.11. Set the default to
something that can actually build targets.
Message-Id: <20220222030207.204401-4-kyle@kyleam.com>
|
|
--cores was added as a synonym for --jobs in v3.10.0 (2012), and, as
of v6.5.0, --cores and --jobs are distinct things for cloud/cluster
jobs. Wait to add --jobs until it's requested.
Message-Id: <20220222030207.204401-3-kyle@kyleam.com>
|
|
Magit switched to Transient for its popups a while go. Magit Popup is
still around for third-party libraries that may use it, but it's not
actively developed.
At the moment, this switch is trading one external library for another
(improved) one. However, Transient will ship with Emacs starting with
the upcoming 28.1 release.
Message-Id: <20220222030207.204401-2-kyle@kyleam.com>
|
|
public-inbox has started to drop dates from its copyright lines,
pointing to the recommendation at
https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/
I regularly fail to keep copyright lines up to date, so I'll gladly
follow suit.
Drop the dates and change the copyright holder to (almost match) the
variants recommended in the above article.
|
|
After GitHub Actions were available, this repository kept using Travis
because it worked well enough, especially given this package is very
much in maintenance mode. However, going forward it'd be nice to use
purcell/setup-emacs action to test various Emacs versions.
Don't bother testing against Emacs 24 because the next release will
bump the minimum Emacs version to at least 25.1.
While touching this setup, drop the Makefile target for downloading
dependencies and instead just expect dependencies to be one level up
from the snakemake-mode checkout.
|
|
--eval uses lexical scoping as of Emacs 27. Load autoload.el to
evaluate (defvar generated-autoload-file ...) and get dynamic scope.
See Emacs's bug#39823.
|
|
|
|
|
|
|
|
Register "container" as both a field key and a top-level command
because an example of both is present in the Snakemake docs.
Reported-by: Nicholas Knoblauch <knoblauch.nicholas@gene.com>
Message-Id: <87eelcak64.fsf@kyleam.com>
|
|
|
|
The Travis builds have started to fail because Snakemake now requires
at least Python 3.7.
|
|
More are on the way.
|
|
|
|
|
|
|
|
|
|
I went with the long lines because that will be rendered more nicely
by GitHub. But this is shown in the text field so it doesn't matter.
|
|
|
|
|
|
|
|
|
|
|
|
I shouldn't rely on the license notice at the top of the files.
|
|
|
|
|
|
|
|
|
|
In Emacs 27, specifically 36b64e087e (Add
'font-lock-maximum-decoration' levels for Python, 2018-07-19),
python-font-lock-keywords was changed to a list of symbols that define
different fontification levels, so we can no longer simply tack
snakemake-font-lock-keywords onto it.
Instead define a set of levels that mirrors Python mode's. For
Snakemake mode, the same decoration is used for all levels, but at
least we will honor the level of decoration that the user has set for
Python.
Reported-by: Nicholas Knoblauch <nwknoblauch@gmail.com>
Closes #29.
|
|
This will make it easier to work around a change to
python-font-lock-keywords in Emacs 27.
|
|
snakemake-font-lock-keywords is extended with
python-font-lock-keywords, but the non-keyword bits that python.el
defines for font-lock-defaults are discarded. Keep those too because
python.el sets a value for font-lock-syntactic-face-function.
|
|
|
|
There are few enough entries in each release that this extra structure
isn't really helpful. Plus, some things that are labeled as "new
features", like recognizing keywords for fontification, seem a bit
silly to call a feature, but I can't think of a better heading for
them.
|
|
|
|
|
|
This should have been adjusted in a5f868f (Change 'guix environment'
snippet to use --manifest, 2018-09-01).
|
|
|
|
|
|
With the addition of 'report', the built-in names and command names
are no longer disjoint sets. All occurrences of 'report' are
fontified as a built-in because the built-in regexp is a substring of
the command regexp. Move the command regexp before the built-in
regexp so that the 'report:' command is highlighted as a command.
|
|
|
|
This has been around forever.
|
|
|
|
|
|
|
|
'guix environment' accepts a manifest as of 267379f85 (environment:
Add --manifest option., 2018-02-15). Declaring a set of dependencies
via --manifest is more straightforward than doing so with --load, so
suggest --manifest instead.
|
|
Match the order given in guix-snakemake-environment.
|
|
Using "/usr/bin/env" there is silly. We can rely on "/bin/sh" being
present more than "/usr/bin/env".
|