[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why isn't python-check-custom-command permanent buffer local?
|
From: |
Sam Steingold |
|
Subject: |
Re: why isn't python-check-custom-command permanent buffer local? |
|
Date: |
Mon, 26 Jan 2015 17:55:43 -0500 |
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
<address@hidden> 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/>