From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Mark E. Shoulson" <mark@shoulson.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: 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/)]
Date: Wed, 06 May 2020 02:17:44 +0200 [thread overview]
Message-ID: <87tv0tc3x3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <3996850e-cf9a-57b5-25a5-8f9bf392c7aa@kli.org> (Mark E. Shoulson's message of "Thu, 16 Jan 2020 16:57:55 -0500")
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
prev parent reply other threads:[~2020-05-06 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 21:57 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
2020-05-06 0:17 ` Nicolas Goaziou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv0tc3x3.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mark@shoulson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).