Bug: org-ellipsis does not work as a local variable [9.3.1 (release_9.3.1-95-gf93020 @ /home/mark/git-repos/org-mode/lisp/)]

Bug: org-ellipsis does not work as a local variable [9.3.1 (release_9.3.1-95-gf93020 @ /home/mark/git-repos/org-mode/lisp/)]

[Mark E. Shoulson]

[-- Attachment #1: Type: text/html, Size: 11735 bytes --]

Re: Bug: org-ellipsis does not work as a local variable [9.3.1 (release_9.3.1-95-gf93020 @ /home/mark/git-repos/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

"Mark E. Shoulson" <mark@shoulson.com> writes:

> The "org-ellipsis" variable is specifically marked as (potentially) a
> safe local variable, so obviously someone intended for it possibly to be
> used that, and believed that it might be useful to someone as a local
> variable.
>
> However, there is no setup that I can find which makes this work.
> Placing
>
> :  #  Local Variables:
> :  #  org-ellipsis: "XXX"
> :  #  End:
>
> at the end of the file, or setting it in the top line, makes no change
> in the ellipsis, even if you do M-x org-mode again or reload the file
> (with find-alternate-file).  Indeed, M-x org-mode clears the local value
> assignment altogether.  Setting it by hand with setq-local doesn't work
> (it is cleared when you do M-x org-mode again anyway, as mentioned.)
>
> So, is org-ellipsis really not meant ever to be a local variable?  If
> so, that likely should be documented, and certainly the :safe annotation
> on it should be removed, as it strongly implies that using it as a local
> variable is acceptable and useful.

I removed :safe keyword and specified it isn't meant to be a set as
a local variable in its docstring.

Patches are welcome to enable it, tho.

Thank you for the report.

Regards,

-- 
Nicolas Goaziou