* why isn't python-check-custom-command permanent buffer local?
@ 2015-01-26 19:54 Sam Steingold
2015-01-26 22:50 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Sam Steingold @ 2015-01-26 19:54 UTC (permalink / raw)
To: emacs-devel; +Cc: fgallina
IMO python-check-custom-command should be permanent buffer local.
unless someone explains why not, I will make it so.
Thanks
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1343
http://www.childpsy.net/ http://ffii.org http://iris.org.il http://memri.org
http://think-israel.org http://dhimmi.org http://americancensorship.org
Feynman: 'Philosophy of science is as useful to scientists as ornithology is to birds'
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: why isn't python-check-custom-command permanent buffer local?
2015-01-26 19:54 why isn't python-check-custom-command permanent buffer local? Sam Steingold
@ 2015-01-26 22:50 ` Stefan Monnier
2015-01-26 22:55 ` Sam Steingold
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2015-01-26 22:50 UTC (permalink / raw)
To: Sam Steingold; +Cc: fgallina, emacs-devel
> IMO python-check-custom-command should be permanent buffer local.
> unless someone explains why not, I will make it so.
Could you explain why it should be permanent-local?
Or do you just mean it should be made buffer-local? I guess replacing
the `setq' with a `setq-local'would make a lot of sense, tho since it
probably contains the buffer-file-name.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: why isn't python-check-custom-command permanent buffer local?
2015-01-26 22:50 ` Stefan Monnier
@ 2015-01-26 22:55 ` Sam Steingold
2015-01-27 2:01 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Sam Steingold @ 2015-01-26 22:55 UTC (permalink / raw)
To: Stefan Monnier; +Cc: fgallina, emacs-devel
I am sorry, my fault, of course I meant exactly what you said, and for
the reason you mention.
On Mon, Jan 26, 2015 at 5:50 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> IMO python-check-custom-command should be permanent buffer local.
>> unless someone explains why not, I will make it so.
>
> Could you explain why it should be permanent-local?
> Or do you just mean it should be made buffer-local? I guess replacing
> the `setq' with a `setq-local'would make a lot of sense, tho since it
> probably contains the buffer-file-name.
>
>
> Stefan
--
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net/>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: why isn't python-check-custom-command permanent buffer local?
2015-01-26 22:55 ` Sam Steingold
@ 2015-01-27 2:01 ` Stefan Monnier
0 siblings, 0 replies; 4+ messages in thread
From: Stefan Monnier @ 2015-01-27 2:01 UTC (permalink / raw)
To: Sam Steingold; +Cc: fgallina, emacs-devel
> I am sorry, my fault, of course I meant exactly what you said, and for
> the reason you mention.
Sorry, then let me rephrase my previous answer:
>>> IMO python-check-custom-command should be permanent buffer local.
>>> unless someone explains why not, I will make it so.
Over my dead body!
Are you out of your mind?
¡¡It should be buffer local!!
Stefan "go ahead, and thank you"
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-01-27 2:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-26 19:54 why isn't python-check-custom-command permanent buffer local? Sam Steingold
2015-01-26 22:50 ` Stefan Monnier
2015-01-26 22:55 ` Sam Steingold
2015-01-27 2:01 ` Stefan Monnier
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).