Thorsten Jolitz <tjol...@gmail.com> writes:
> Alexander Baier <alexander.ba...@mailbox.org> writes:
>
>> On 2014-07-07 16:40 Grant Rettke wrote:
>>> That property then is something that we may set as a buffer local
>>> variable set in the file itself for cases where want only months in
>>> the entire file?
>>
>> File local variables?
>
> ,----[ C-h f make-variable-buffer-local RET ]
> | make-variable-buffer-local is an interactive built-in function in `C
> | source code'.
> | [...]
> `----
>
> Aren't file-local and buffer-local variable really aliases? In the Emacs
> world both names are used, but they seem to refer to the same thing,
> except maybe that file-local vars are defined persistently in the file?
> Not sure really ...
Not really: a buffer may or may not be associated with a file, so its
buffer-locals cannot possibly be file-locals. Ditto for a buffer that
*is* associated with a file, but which then is given a bunch of
buffer-locals (e.g. associated with a minor mode for that file).
OTOH, file-locals are read from the file when the file is opened and
they *do* become buffer-local at that point.
And yes, file-locals could be used to satisfy the OP's first request.
AFAIK, there is no way to satisfy the second request (i.e. for only
parts of the file). org-time-stamp-custom-formats is for visual display
only: the underlying timestamp is standard ISO and the custom one is
overlaid iff org-display-custom-times is set (but if I read the
docstring correctly, the custom format is honored during export in this
case, so it is a bit more than visual display). However, there is no way
to have that variable set one way for part of the file and another way
for a different part.
Nick
