| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Closes #24.
|
|
Closes #22.
|
|
|
|
Snakemake commands are currently executed through compile. In
general, this works fine, but it doesn't work well when Snakemake
should be executed in a different environment than the one in which
the current Emacs session was started. For example, Guix commands
like 'guix environment ...' manipulate environmental variables to
expose particular software. With the current setup, snakemake-program
could be set to a wrapper script that creates the environment and then
calls Snakemake:
guix environment -l manifest.scm --ad-hoc snakemake --pure \
-- snakemake $@
But the disadvantage of this approach is that it adds the
environmental setup time to _each_ Snakemake call.
To work better with tools like Guix, let's add an alternative
interface that allows commands to be executed in a terminal session.
Instead of the above script, snakemake-shell-file-name can be set to a
script with
guix environment -l manifest.scm --ad-hoc snakemake --pure
Now the environmental setup cost is limited to starting the terminal.
|
|
|
|
|
|
|
|
|
|
wildcard_constraints was added in Snakemake v3.8.0 (feb6aee).
|
|
|
|
|
|
|
|
Closes #15.
|
|
|
|
|
|
|
|
Re: #9
|
|
This keyword was added in Snakemake version 3.5.5.
|
|
|
|
https://groups.google.com/d/msg/snakemake/segLE-RlV_s/nQCTxH_TJwAJ
|
|
|
|
|
|
This keyword was added in Snakemake 3.5.
|
|
|
|
|
|
|
|
|
|
The touch flag was just recently documented:
https://groups.google.com/d/msg/Snakemake/ZxUo20DV2KE/0S1rBj0XzwQJ
|
|
|
|
|
|
- Change continued field values to support Python indentation. This
is useful when the value is using something like format (but only
applies to naked field keys).
- Don't move back to the start of the line when in a continued field
value.
- When on the first line of block, only indent to main offset.
- Move to current indentation if point is before it. Unless there is
one possible value for indentation, don't adjust indentation any
further.
|
|
|
|
Previously, indentation was handled only for the first line following
a run value. Extend this to support any field value that starts on
the line below a field key, since that is valid syntax.
|
|
|
|
This was added in version 3.1.
|
|
|
|
|
|
|