[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What magic is saying "obsolete variable"
From: |
Lennart Borgman |
Subject: |
Re: What magic is saying "obsolete variable" |
Date: |
Sat, 18 Dec 2010 20:54:14 +0100 |
On Sat, Dec 18, 2010 at 4:50 PM, Stefan Monnier
<address@hidden> wrote:
>> When stepping through this in edebug
>
>> (mumamo-save-buffer-state nil
>> (remove-list-of-text-properties (point-min) (point-max)
>> (list 'fontified)))
>
>> I get the warning below after passing the next last `)':
>
>> Warning: `font-lock-beginning-of-syntax-function' is an obsolete variable
>> (as
>> of Emacs 23.3); use `syntax-begin-function' instead.
>
> This warning comes from the byte-compiler. I have no idea why the
> byte-compiler is called during your edebug.
>
>> The macro `mumamo-save-buffer-state' is just a copy of
>> save-buffer-state in font-lock.el (which is not exposed by
>> font-lock.el).
>
> Newer Emacsen have the macro with-silent-modifications for that, so you
> may want to use that one (or a copy of it) instead.
Thanks, I have forgotten to switch to a copy of that.
However this is very similar to the save-buffer-state so I guess it is
not involved here. The differences involved are just
(declare (debug t) (indent 0)) =new=> (declare (indent 1) (debug let))
and an unwind-protect in the new macro.