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>
Cc: Kyle Meyer <kyle@kyleam.com>, Comment <comment@noreply.github.com>
Subject: Re: Not consider "input" a python keyword? (#20)
Date: Thu, 17 Nov 2016 23:07:09 -0800	[thread overview]
Message-ID: <kyleam/snakemake-mode/issues/20/261463714@github.com> (raw)
In-Reply-To: <kyleam/snakemake-mode/issues/20@github.com>

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

Thanks! Will do within the next week :)

On Fri, Nov 18, 2016 at 12:27 AM, Kyle Meyer <notifications@github.com>

> I'm OK overriding python-font-lock-keywords and removing the
> highlighting of "input", but I wonder whether it's better to go the
> other way.
> I've taken the second approach in the km/rx-builtin branch, if you
> want to test it out and see how you feel about the additional
> highlighting.
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kyleam/snakemake-mode/issues/20#issuecomment-261402794>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQ9I0rgF7ITdGtWir1O22ylnKaSBl28Iks5q_OLTgaJpZM4K1A3Q>
> .

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:

[-- Attachment #2: Type: text/html, Size: 3560 bytes --]

  parent reply	other threads:[~2016-11-18  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  8:47 Endre Bakken Stovner
2016-11-17 23:05 ` Kyle Meyer
2016-11-17 23:27 ` Kyle Meyer
2016-11-18  7:07 ` Endre Bakken Stovner [this message]
2016-11-22  8:10 ` Endre Bakken Stovner
2016-11-22 23:39 ` Kyle Meyer
2016-11-22 23:40 ` 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/20/261463714@github.com \
    --to=notifications@github.com \
    --cc=comment@noreply.github.com \
    --cc=kyle@kyleam.com \
    --cc=reply+0013cd7c1af55bdd2a0bff75d5d7685b0ce0df1321846c3b92cf0000000114466a9d92a169ce0b52d6d3@reply.github.com \
    --cc=snakemake-mode@noreply.github.com \
    --subject='Re: Not consider "input" a python keyword? (#20)' \


* 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).