From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Refactoring flymake.el
Date: Fri, 18 Aug 2017 16:32:20 -0400 [thread overview]
Message-ID: <jwv378oaaia.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: lzr2w9x72s.fsf@gnu.org
>> Can you add some file-local settings in them?
> elpy (https://github.com/jorgenschaefer/elpy) ignores them.
> I just tried
> --8<---------------cut here---------------start------------->8---
> # Local Variables:
> # flymake-mode: nil
> # End:
> --8<---------------cut here---------------end--------------->8---
> and flymake is still enabled in scratch.
> So -- no, file-local settings do not solve my problem.
We can add code to provide a new var, instead of adding the code you
added. Then the behavior can be configured via file-local or
dir-local settings.
So my question was whether in your use case it's practical to add
file-local settings.
>> Using file-local or dir-local variables settings is often more convenient.
> Nope, because I have to deal with the "safe local variable dialogue"
> every time I visit such a file.
Such questions should only show up if the var doesn't have a proper
safe-local-variable property set.
Stefan
next prev parent reply other threads:[~2017-08-18 20:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:40 Refactoring flymake.el João Távora
2017-08-17 16:57 ` John Wiegley
2017-08-17 18:08 ` Sam Steingold
2017-08-17 22:32 ` Stefan Monnier
2017-08-18 14:51 ` Sam Steingold
2017-08-18 15:11 ` Dmitry Gutov
2017-08-18 16:13 ` Sam Steingold
2017-08-18 16:25 ` Dmitry Gutov
2017-08-18 17:59 ` Sam Steingold
2017-08-18 18:52 ` Noam Postavsky
2017-08-18 19:38 ` Sam Steingold
2017-08-18 16:26 ` Clément Pit-Claudel
2017-08-18 20:32 ` Stefan Monnier [this message]
2017-08-18 13:04 ` Dmitry Gutov
2017-08-18 19:20 ` João Távora
2017-08-19 1:59 ` Leo Liu
2017-08-21 12:50 ` Refactoring flymake.el - jumped the gun João Távora
2017-08-23 3:30 ` Stefan Monnier
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=jwv378oaaia.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).