From: Robert Klein <RoKlein@roklein.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: tentative patch Re: commit found, was: Re: ECM for: issues with publishing to LaTeX using #INCLUDE
Date: Sun, 21 Jun 2015 14:55:22 +0200 [thread overview]
Message-ID: <20150621145522.6d13b2da@zotac> (raw)
In-Reply-To: <87oaka58mi.fsf@selenimh.access.network>
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]
Hello,
you're right about eval and symbol-value, of course. I mixed up my test
files, so both the commit I `identified' and the `patch' are bogus.
I now used git bisect for both my current minimal setup (.emacs
attached as .femacs and the files ~/ot/1.org, ~/ot/2.org, and
~/ot/3.org all three having the contents of the attached file 1.org)
and the setup and project I first encountered the issue.
The issue occurs always during publishing the _second_ file, that is,
the first file being published gets published Ok, and the following
files don't.
For the minimal example I cd'd to ~/ot and called emacs using the
command line:
rm *.tex ~/.org-timestamps/linux-e-pdf.cache ; emacs -q -l ~/.femacs
For the original project I used my full setup but also deleted *.tex,
*.pdf, and ~/.org-timestamps/linux-e-pdf.cache.
To be sure nothing went wrong I bisected twice for each project.
For the minimal example commit 2965f8fb0c048a20b52ba90627e7cca6fe706c93
is identified as the first bad one.
For my full setup it is the earlier commit
69dd4301ab7aeb581968f1c7e75167338d024c8f.
My Emacs version is : GNU Emacs 24.5.1 (x86_64-suse-linux-gnu, GTK+
Version 3.10.2) of 2015-04-30 on build83
Meanwhile I added a second elisp source and call (between
latex_class_options and the later options line). With this added I
don't see the error anymore. Same for the minimal example (org files
all having the content of the attached file working.org)
I'm sorry for the earlier confusion.
Best regards
Robert
On Sun, 21 Jun 2015 00:15:49 +0200
Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Robert Klein <RoKlein@roklein.de> writes:
>
> > when I change a `symbol-value' in the commit back to `eval', export
> > seems to work again.
>
> Actually, I cannot reproduce your issue.
>
> > Patch is attached.
>
> I don't understand why replacing `symbol-value' with `eval' could
> solve the issue. Could you debug this and see what happens with both
> `symbol-value' and `eval'?
>
> Thank you.
>
> Regards,
>
[-- Attachment #2: 1.org --]
[-- Type: application/octet-stream, Size: 446 bytes --]
#+TITLE: Frequently Asked Questions
#+name: docinfo
#+begin_src elisp :exports none
(let ((props (org-export-get-environment)))
(concat "#+LaTeX_HEADER: \\newcommand{\\myTitle}{"
(org-element-interpret-data
(plist-get props :title))
"}\n"))
#+end_src
#+CALL: docinfo() :exports results :results raw
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [11pt]
#+OPTIONS: email:t
* Headline
Some Text
[-- Attachment #3: .femacs --]
[-- Type: application/octet-stream, Size: 1152 bytes --]
(setq load-path (cons "~/.emacs.d/org-mode/lisp" load-path))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org)
(setq org-latex-classes
'(("scrartcl"
"\\documentclass[11pt]{scrartcl}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
("article"
"\\documentclass[11pt]{article}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))))
(setq org-confirm-babel-evaluate nil)
(setq org-publish-project-alist nil)
(add-to-list 'org-publish-project-alist
'("linux-e-pdf"
:base-directory "~/ot"
:base-extension "org"
:publishing-directory "~/ot"
:publishing-function org-latex-publish-to-latex
))
(org-publish "linux-e-pdf")
[-- Attachment #4: working.org --]
[-- Type: application/octet-stream, Size: 837 bytes --]
#+TITLE: Frequently Asked Questions
#+name: docinfo
#+begin_src elisp :exports none
(let ((props (org-export-get-environment)))
(concat "#+LaTeX_HEADER: \\newcommand{\\myTitle}{"
(org-element-interpret-data
(plist-get props :title))
"}\n"))
#+end_src
#+CALL: docinfo() :exports results :results raw
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [11pt]
#+name: htmlpdflink
#+begin_src elisp :exports none
(let ((props (org-export-get-environment)))
(concat "#+HTML: <a href=\""
(car (last (split-string
(file-name-sans-extension (buffer-file-name))
"/")))
".pdf\">PDF-Version</a>\n"))
#+end_src
#+CALL: htmlpdflink() :exports results :results raw
#+OPTIONS: email:t
* Headline
Some Text
next prev parent reply other threads:[~2015-06-21 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 18:04 issues with publishing to LaTeX using #INCLUDE Robert Klein
2015-06-18 6:58 ` Robert Klein
2015-06-18 7:15 ` ECM for: " Robert Klein
2015-06-18 7:21 ` Robert Klein
2015-06-18 7:55 ` Nicolas Goaziou
2015-06-18 12:21 ` Robert Klein
2015-06-18 18:51 ` Robert Klein
2015-06-19 7:51 ` commit found, was: " Robert Klein
2015-06-19 18:28 ` tentative patch " Robert Klein
2015-06-20 22:15 ` Nicolas Goaziou
2015-06-21 12:55 ` Robert Klein [this message]
2015-06-22 8:37 ` Nicolas Goaziou
2015-06-22 15:01 ` Robert Klein
2015-06-23 21:44 ` Nicolas Goaziou
2015-06-24 7:07 ` Robert Klein
2015-06-25 13:16 ` Nicolas Goaziou
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=20150621145522.6d13b2da@zotac \
--to=roklein@roklein.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).