Re: Can we expand the valid location of "Local Variables" ?

[Stefan Monnier <monnier@iro.umontreal.ca>]

> Probably we'd want to make this into a variable? And the default maybe
> should be higher than 3000?

I don't like having this 3000 hard-coded everywhere, so making
a variable makes sense.

But encouraging large "Local Variables" blocks is a bad idea, IMO, so
I'd keep it at 3000 and I wouldn't care to document the var either.
I'd even be happy with a "--" in its name.

> The use case where I hit this was in an .org file that was defining a
> presentation where I needed to control the export with an eval: (progn
> ...) block. Org wasn't doing quite what I needed it to, so the block had
> some advice definitions in it, and that pushed the thing over the 3000
> byte limit.

Of course, you can use a short

    eval: (progn (re-search-backward "^(progn ;;local-config") (eval (read (current-buffer))))

and then put an arbitrarily long Elisp chunk anywhere else in the buffer
with a leading `(progn ;;local-config`.


        Stefan