From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 934a72c: User can specify files never subject to flymake.
Date: Fri, 03 Nov 2017 15:42:30 -0400 [thread overview]
Message-ID: <lz60ar409l.fsf@gnu.org> (raw)
In-Reply-To: 87inertdj4.fsf@gmail.com
> * João Távora <wbnbgniben@tznvy.pbz> [2017-11-03 18:36:47 +0000]:
>
> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
>>> * lisp/progmodes/flymake-proc.el (flymake-proc-ignored-file-name-regexps):
>>> Add user customization option.
>>
>> Shouldn't this be in flymake.el and apply to all flymake backends rather
>> than only those using flymake-proc?
>
> Also Sam, shouldn't this commit already take care of your specific problem?
>
> de3a3ed034467ff2529c8262600e8a249969fd14
> Author: Sam Steingold <sds@gnu.org>
> Date: Mon Aug 21 09:48:14 2017 -0400
>
> allow nil init in flymake-allowed-file-name-masks to disable flymake
>
> Or did I break it in the process?
I think you did, it no longer works.
Also, it relies on the "disabling" record to come before the "enabling"
one, so it was not such a good idea in the first place.
Thanks for you work on flymake!
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://memri.org http://jij.org http://www.dhimmitude.org http://no2bds.org
He who laughs last thinks slowest.
prev parent reply other threads:[~2017-11-03 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171101134009.18554.21992@vcs0.savannah.gnu.org>
[not found] ` <20171101134010.1A70A209B1@vcs0.savannah.gnu.org>
2017-11-01 14:15 ` [Emacs-diffs] master 934a72c: User can specify files never subject to flymake Stefan Monnier
2017-11-01 21:26 ` Sam Steingold
2017-11-02 20:59 ` Stefan Monnier
2017-11-03 15:50 ` Sam Steingold
2017-11-03 18:50 ` João Távora
2017-11-03 19:48 ` Sam Steingold
2017-11-03 18:36 ` João Távora
2017-11-03 19:42 ` Sam Steingold [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lz60ar409l.fsf@gnu.org \
--to=sds@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.