From: Endre Bakken Stovner <email@example.com>
To: kyleam/snakemake-mode <firstname.lastname@example.org>
Subject: Use snakemake-mode automatically on .rule extension? (#15)
Date: Mon, 02 May 2016 05:04:44 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
The official snakemake workflow repository uses this extension for files containing rules (i.e. are `include:d` in snakefiles, but not meant to be run by themselves).
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
[-- Attachment #2: Type: text/html, Size: 957 bytes --]
next reply other threads:[~2016-05-02 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 12:04 Endre Bakken Stovner [this message]
2020-04-17 0:10 ` Use snakemake-mode automatically on .rule extension? (#15) Kyle Meyer
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://git.kyleam.com/snakemake-mode
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).