emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Protesilaos Stavrou <public@protesilaos.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Export does not read .dir-locals.el [9.7.3 (release_9.7.3 @ /usr/local/share/emacs/30.0.50/lisp/org/)]
Date: Fri, 14 Jun 2024 07:53:55 +0300	[thread overview]
Message-ID: <87msno3z18.fsf@protesilaos.com> (raw)

Dear maintainer,

I have noticed that the export mechanism does not read the local
variables of a file when those come from a .dir-locals.el.

Steps to reproduce this:

1. Create a test directory.

2. Inside of that directory, write a .dir-locals.el file with something
   like the following:

     ;;; Directory Local Variables            -*- no-byte-compile: t -*-
     ;;; For more information see (info "(emacs) Directory Variables")

     ((nil . ((testing . "hello"))))

3. Now create a new Org file with a code block that includes the
   variable we introduced in the previous step. For example:

      Does this export?

      #+begin_src emacs-lisp :exports results
      testing
      #+end_src

4. If you do C-c C-c on the code block, it returns the local value as
   the variable is not void. But if you try to export, you an error that
   the variable is void.

Perhaps there is some user option to let the export mechanism read those
local variables?

All the best,
Protesilaos (or simply "Prot")

* * *

Emacs  : GNU Emacs 30.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.38, cairo version 1.16.0)
 of 2024-06-11
Package: Org mode version 9.7.3 (release_9.7.3 @ /usr/local/share/emacs/30.0.50/lisp/org/)

-- 
Protesilaos Stavrou
https://protesilaos.com

next             reply	other threads:[~2024-06-14  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  4:53 Protesilaos Stavrou [this message]
2024-06-14 14:27 ` [BUG] Export does not read .dir-locals.el [9.7.3 (release_9.7.3 @ /usr/local/share/emacs/30.0.50/lisp/org/)] Ihor Radchenko
2024-06-18  9:48   ` Protesilaos Stavrou

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=87msno3z18.fsf@protesilaos.com \
    --to=public@protesilaos.com \
    --cc=emacs-orgmode@gnu.org \
    /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

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