diff options
author | Kyle Meyer <kyle@kyleam.com> | 2017-03-26 19:06:46 -0400 |
---|---|---|
committer | Kyle Meyer <kyle@kyleam.com> | 2017-03-26 21:21:31 -0400 |
commit | f2ea2ab6423f223b6dae3e1f8feab60da0745ec4 (patch) | |
tree | f4ca1b1e1ad59718d3ca149ab12d5f336287f722 /NEWS | |
parent | 7ffea30d691cd7a46b6969767b6840dabaaea428 (diff) | |
download | snakemake-mode-f2ea2ab6423f223b6dae3e1f8feab60da0745ec4.tar.gz |
Add a terminal interface for running Snakemake
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.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -1,5 +1,15 @@ NEWS -- history of user-visible changes -*- mode: org; -*- +* master (unreleased) + +** New features + +- ~snakemake-popup~ commands learned to call Snakemake through a + terminal rather than through ~compile~. This allows a persistent + environment to be maintained between Snakemake calls, which is + useful for running Snakemake in isolated environments created by + tools like Guix. + * v1.1.0 ** New features |