emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Why may some Org regexps be risky when set as buffer-local variables?
Date: Sat, 29 Mar 2014 14:54:37 +0100	[thread overview]
Message-ID: <87siq1m7oi.fsf@gmail.com> (raw)
In-Reply-To: 87lhvtkvev.fsf@gmail.com

Nick Dokos <ndokos@gmail.com> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>> Hi List, 
>> there are dozens of regexps that are set as buffer-local variables when
>> org-mode is turned on as major-mode, but other regexps are defined and
>> set only once as global variables when e.g. org.el is loaded, and the
>> docstring of these variables often reads like this:
>> ,---------------------------------------------------------------
>> | org-block-regexp is a variable defined in `org.el'.
>> | Its value is [...]
>> | 
>> |   This variable may be risky if used as a file-local variable.
>> | 
>> | Documentation:
>> | Regular expression for hiding blocks.
>> `---------------------------------------------------------------
>> Why are these variables considered risky when used as a file-local
>> variables? Was this "risk" the prime reason to make them global - or are
>> they global simply because there was no special reason to make them
>> buffer-local? 
> All it means is that nobody has gone to the trouble of certifying them
> as safe. By default, file local variable are considered risky. See
>   (info "(emacs) Safe File Variables")
> for more.

Ok, then as long as these variables hold strings there is no risk anyway
since e.g. (eval "(+ 2 2)") gives "(+ 2 2)" and not 4. Thanks.


      reply	other threads:[~2014-03-29 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 11:46 Why may some Org regexps be risky when set as buffer-local variables? Thorsten Jolitz
2014-03-29 13:04 ` Nick Dokos
2014-03-29 13:54   ` Thorsten Jolitz [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:

  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=87siq1m7oi.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).