[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why isn't python-check-custom-command permanent buffer local?
|
From: |
Stefan Monnier |
|
Subject: |
Re: why isn't python-check-custom-command permanent buffer local? |
|
Date: |
Mon, 26 Jan 2015 17:50:47 -0500 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
> 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