Re: Buffer-local variables affect general-purpose functions

[Stefan Monnier]

> Paul seemed to say something more broad: that _all_ behaviors specific
> to unibyte buffers should go away.  Do you agree?

Too broad to answer.  I think this needs to be decided on a case-by-case basis.

> Anyway, what should replace those hacks?  Arbitrarily interpreting raw
> bytes as Latin characters is not TRT, IMO.

I think it is: char-equal compares *chars*, not *bytes*.  IOW it's a bug
to pass bytes to it.

> Maybe so, but something like
>   (with-buffer-defaults BODY)
> might be the solution, and should be easy enough to implement.
> Or maybe some other way of telling primitives: don't apply
> buffer-specific behavior to this code.

That might be a valid option, but in any case it's incompatible and the
incompatibility will have different consequences for different uses, so
we're back to "case-by-case basis".


        Stefan