discussion and development of Emacs Snakemake mode
 help / color / mirror / code / Atom feed
From: Endre Bakken Stovner <notifications@github.com>
To: kyleam/snakemake-mode <snakemake-mode@noreply.github.com>
Subject: yapf for snakefiles (#18)
Date: Fri, 08 Jul 2016 00:41:36 -0700	[thread overview]
Message-ID: <kyleam/snakemake-mode/issues/18@github.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

Would you be interested in having [yapf](https://github.com/google/yapf) for snakefiles? If you think it is desirable and feasible, I might start looking into it. I guess at first only yapfing the `rule:` portion should be the goal. 

In the end hacking yapf to analyze snakefiles might be a goal...

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: 1239 bytes --]

             reply	other threads:[~2016-07-08  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  7:41 Endre Bakken Stovner [this message]
2016-07-08  8:03 ` Endre Bakken Stovner
2020-04-14  2:10   ` Kyle Meyer
2016-07-09 11:18 ` Endre Bakken Stovner
2020-04-14  2:11   ` Kyle Meyer
2016-10-21 21:30 ` Kyle Meyer

Reply instructions:

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 \
    --in-reply-to=kyleam/snakemake-mode/issues/18@github.com \
    --to=notifications@github.com \
    --cc=reply+0013cd7c0a0d6d84e0fc68ca2835c538fd845ca895959bd192cf0000000113971b3092a169ce09cdb427@reply.github.com \
    --cc=snakemake-mode@noreply.github.com \
    --subject='Re: yapf for snakefiles (#18)' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).