Re: frame-local variables weirdness

[Stefan Monnier]

>     I'm suggesting we introduce a new concept which we could call "specifier"
>     or "localizable quasi variable".  We could create them with:

>        (defconst new-interprogram-cut-function
>                  (make-specifier 'x-select-text))

>     Now new-interprogram-cut-function is a normal global variable (actually
>     a constant: we will never `setq' it).  Its value is a "specifier".

>     Then we get get the value of this specifier with:

>        (specifier-value new-interprogram-cut-function)

> What we have now, where the variable itself has different bindings in
> different contexts, is much cleaner.

Could you expand on what you think makes it cleaner?
The above also gives it different bindings in different contexts: the only
difference is that it's not a variable any more, so you can't let-bind it.


        Stefan