all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Samuel Bronson <naesten@gmail.com>
Cc: 17949@debbugs.gnu.org
Subject: bug#17949: 24.3; .dir-locals.el needs a way to construct paths relative to its own location
Date: Tue, 08 Jul 2014 14:17:41 -0400	[thread overview]
Message-ID: <jwvtx6rracm.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <878uo7pl0x.fsf@naesten.mooo.com> (Samuel Bronson's message of "Sat, 05 Jul 2014 17:12:46 -0400")

> Sometimes, I want to use .dir-locals.el to set a variable to refer to a
> specific file within the tree in question, independantly of how deep in
> that tree the file in question actually is.

You could use something like:

   (eval (setq-local my-var
                     (expand-file-name "etc/foo"
                                       (locate-dominating-file
                                        default-directory ".dir-locals.el"))))

> Perhaps using a form something like:
>     ,(expand-file-name "etc/foo.bar" dir-locals-directory)

Problem is security: the .dir-local.el file might not be under your
control, so we don't want to run arbitrary code.  The "eval" option
above of course suffers from the same problem, but at least it's the
official existing way to run arbitrary code, which means it doesn't run
that code silently unless you've previous accepted it as "safe".

This said, it might indeed be handy to be able to use , like you suggest
(tho it too would need to go though some "security check", of course).


        Stefan





  reply	other threads:[~2014-07-08 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 21:12 bug#17949: 24.3; .dir-locals.el needs a way to construct paths relative to its own location Samuel Bronson
2014-07-08 18:17 ` Stefan Monnier [this message]
2021-05-29  5:09   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvtx6rracm.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17949@debbugs.gnu.org \
    --cc=naesten@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.