[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problems setting byte-compile-warnings to t
From: |
Richard Stallman |
Subject: |
Re: Problems setting byte-compile-warnings to t |
Date: |
Sun, 28 Oct 2007 09:51:09 -0400 |
So the simplest fix would seem to adjust the buffer-local value in
inbuffer in the same way that byte-compile-close-variables does.
I see a problem with that: such a change would persist after the end
of the compilation.
Here's another idea: add a function byte-compile-memq which always
returns t if the second arg is t, and use that instead of memq to test
membership in byte-compile-warnings. That avoids the need to alter
data provided by the user. Do you see any problem with it?