Does erase-buffer reset buffer-local variables to nil?

Does erase-buffer reset buffer-local variables to nil?

[Thorsten Jolitz]

Hi List, 

I face the problem that I set a buffer-local variable in one function,
and find its value to be nil later on in another function. In between,
'revert-buffer' is called with a revert-buffer-function that uses
erase-buffer.

I experimented a bit, and during the experiments it seemed that
'erase-buffer' doesn't modify buffer-local vars. But then I don't really
understand how its possible to set a variable (even print out its value
in a message call) in one function, but find its value to be nil again
later on without touching it explicitly in between.

Any hints would be welcome. 

-- 
cheers,
Thorsten

Re: Does erase-buffer reset buffer-local variables to nil?

[Thorsten Jolitz]

Thorsten Jolitz <tjolitz@gmail.com> writes:

> I face the problem that I set a buffer-local variable in one function,
> and find its value to be nil later on in another function. In between,
> 'revert-buffer' is called with a revert-buffer-function that uses
> erase-buffer.

Following up to my own post: 

I figured out that its not 'erase-buffer' that is the culprit, but a
temporary change of major-mode, because by convention:

,-------------------------------------------------------------------------
| The major mode command should start by calling kill-all-local-variables...
`-------------------------------------------------------------------------

-- 
cheers,
Thorsten