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:48:44 -0400 [thread overview]
Message-ID: <lzzi832ler.fsf@gnu.org> (raw)
In-Reply-To: 878tfntcwc.fsf@gmail.com
> * João Távora <wbnbgniben@tznvy.pbz> [2017-11-03 18:50:27 +0000]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>>> * Stefan Monnier <zbaavre@veb.hzbagerny.pn> [2017-11-02 16:59:23 -0400]:
>>>
>>>>>> * 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?
>>>> You might be right, but I don't see any place in flymake.el where file
>>>> names are processed.
>>>
>>> Hmm... indeed. I guess the right thing depends on what's the use-case.
>>> Could you describe the kind of situation in which you need
>>> flymake-proc-ignored-file-name-regexps?
>>
>> I have files scratch.py which are somewhat like a poor man's notebook,
>> with random snippets of code which persist from session to session.
>> flymake using pylint will flag most lines in such files.
>>
>> So I have this in my .emacs:
>>
>> (eval-when-compile (defvar flymake-proc-ignored-file-name-regexps))
>> (eval-after-load "flymake"
>> '(add-to-list 'flymake-proc-ignored-file-name-regexps '"/scratch"))
>
> [Curious, why do you the defvar? Is the FORM of eval-after-load
> byte-compiled?]
Yes.
> Such a facility to disable flymake could be in flymake.el, but perhaps
> it is better if it was already elsewhere in Emacs.
I am not prepared to argue over this, especially since it appears that
Stefan is not particularly happy about the change either.
Basically, elpy enables flymake everywhere and adding
--8<---------------cut here---------------start------------->8---
# Local Variables:
# flymake-mode: nil
# End:
--8<---------------cut here---------------end--------------->8---
to every scratch pad is ugly and _does not work_.
Thanks.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://no2bds.org
https://jihadwatch.org http://honestreporting.com http://think-israel.org
(lisp programmers do it better)
next prev parent reply other threads:[~2017-11-03 19:48 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 [this message]
2017-11-03 18:36 ` João Távora
2017-11-03 19:42 ` Sam Steingold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lzzi832ler.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).