[BUG](?) Export to beamet recently stopped working.

[BUG](?) Export to beamet recently stopped working.

[Emmanuel Charpentier]

[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]

Dear list,

Since about a week, exporting directly to Beamer ceased to work. See
the attached Minimal.org file :

 - This file exports perfectly to a LaTeX file (via C-c C-e l b).

 - The resulting Minimal.tex exports perfectly to Minimal.pdf.

 - Trying to export directly to PDF via C-c C-e l P fails ; content of
the *Messages* buffer :

-----------------
Saving file /home/charpent/Boulot/Cellule
Innovation/BayesDec/Minimal.tex...
Wrote /home/charpent/Boulot/Cellule Innovation/BayesDec/Minimal.tex
Processing LaTeX file Minimal.tex...
Wrong type argument: sequencep, 108
-----------------

 - Ditto when exporting to PDF via C-c C-e l p (= export to PDF withot
making frames at header level 2).

Retrying Beamer PDF export with debug-on-error set to t gives me the
following backtrace :

-----------------
Debugger entered--Lisp error: (wrong-type-argument sequencep 108)
  replace-regexp-in-string("%\\(?:\\(?:bib\\|la\\)tex\\|bib\\)\\>"
#f(compiled-function (m) #<bytecode 0x1587cd8dd641>) 108)
  #f(compiled-function (command) #<bytecode 0x1587cd8dd655>)(108)
  mapcar(#f(compiled-function (command) #<bytecode 0x1587cd8dd655>)
"latexmk -shell-escape -f -pdf -%latex -interaction...")
  org-latex-compile("Minimal.tex")
  org-export-to-file(beamer "Minimal.tex" nil nil nil nil nil org-
latex-compile)
  org-beamer-export-to-pdf(nil nil nil nil)
  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)
-----------------

which isn't very helpful... Any hint would be welcome.

Sincerely yours,

--
Emmanuel Charpentier

PS : CC me would be appreciated : I'm not on the list, and read it via
the archive...


[-- Attachment #2: Minimal.org --]
[-- Type: text/org, Size: 1013 bytes --]

# Pour débugguer l'exportation Beamer

#+begin_src emacs-lisp :exports none :results silent
  (require 'ox-beamer)
  (custom-set-variables
   '(org-latex-pdf-process
     "latexmk -shell-escape -f -pdf -%latex -interaction=nonstopmode -output-directory=%o %f"))
#+end_src


#+language: fr
#+options: tex:t toc:nil H:2
# #+latex_compiler: lualatex
#+latex_compiler: latexmk
#+PANDOC_OPTIONS: pdf-engine:latexmk
#+PANDOC_OPTIONS: pdf-engine-opt=-shell-escape
#+PANDOC_OPTIONS: standalone:t 
#+property: header-args:sage :session

#+latex_compiler: lualatex
#+latex_class: beamer
#+latex_class_options: [french]
#+latex-header: \usetheme{AnnArbor}
#+latex-header: \usefonttheme{professionalfonts}
#+Latex_header: \usepackage{fontspec}
#+latex_header: \usepackage{unicode-math}
#+latex_header: \setsansfont{Fira Sans}
#+latex_header: \setmathfont{Fira Math}
#+latex_header: \usepackage{babel}
#+latex_header: \usepackage[newfloat]{minted}

#+title: Essais ~beamer~ de ~org~.
#+subtitle: Un orteil dans l'Arctique...

Re: [BUG](?) Export to beamet recently stopped working.

[Fraga, Eric]

On Thursday, 11 Aug 2022 at 10:00, Emmanuel Charpentier wrote:
> Since about a week, exporting directly to Beamer ceased to work. See
> the attached Minimal.org file :
> Debugger entered--Lisp error: (wrong-type-argument sequencep 108)

org-latex-pdf-process should be a list of strings, not a string.  Also,
I would not use custom-set-variables but simply set the value locally:

#+begin_src emacs-lisp :exports none :results silent
  (require 'ox-beamer)
  (setq-local org-latex-pdf-process
     '("latexmk -shell-escape -f -pdf -%latex -interaction=nonstopmode -output-directory=%o %f"))
#+end_src

-- 
: Eric S Fraga, with org release_9.5.4-720-g4db67d in Emacs 29.0.50

Re: [BUG](?) Export to beamet recently stopped working.

[Emmanuel Charpentier]

Le jeudi 11 août 2022 à 09:48 +0000, Fraga, Eric a écrit :
> On Thursday, 11 Aug 2022 at 10:00, Emmanuel Charpentier wrote:
> > Since about a week, exporting directly to Beamer ceased to work.
> > See
> > the attached Minimal.org file :
> > Debugger entered--Lisp error: (wrong-type-argument sequencep 108)
> 
> org-latex-pdf-process should be a list of strings, not a string. 

Aaaarghhh... You're right. This works perfectly.
Old age is a wreckage...

> Also,
> I would not use custom-set-variables but simply set the value
> locally:
> 
> #+begin_src emacs-lisp :exports none :results silent
>   (require 'ox-beamer)
>   (setq-local org-latex-pdf-process
>      '("latexmk -shell-escape -f -pdf -%latex -
> interaction=nonstopmode -output-directory=%o %f"))
> #+end_src

Why locally ?
What's the point ?
I don't doubt that it exists, but I don't see it.

Anyway, thank you very much !

--
Emmanuel Charpentier
Now, where is that wakisashi ?...

Re: [BUG](?) Export to beamet recently stopped working.

[Fraga, Eric]

On Thursday, 11 Aug 2022 at 13:51, Emmanuel Charpentier wrote:
> Aaaarghhh... You're right. This works perfectly.

Great!

> Why locally ?

In case you have different configurations.  But if you are happy with
this as a global value, just use setq instead.  I tend to configure each
(large) org document with local settings so that they don't interfere
with each other.

-- 
: Eric S Fraga, with org release_9.5.4-720-g4db67d in Emacs 29.0.50

Re: [BUG](?) Export to beamet recently stopped working.

[Emmanuel Charpentier]

Le jeudi 11 août 2022 à 12:32 +0000, Fraga, Eric a écrit :
> On Thursday, 11 Aug 2022 at 13:51, Emmanuel Charpentier wrote:

[ Snip... ]

> > Why locally ?
> 
> In case you have different configurations.

Nice idea ! I was (still am) aiming at a "default configuration" I
could slap on my .init.el. But your idea  of local configuration might
go on document templates.

>   But if you are happy with
> this as a global value, just use setq instead.  I tend to configure
> each
> (large) org document with local settings so that they don't interfere
> with each other.

What about emacs' "custom" interface ? Do you use it ?

Thanks again !

Re: [BUG](?) Export to beamet recently stopped working.

[Fraga, Eric]

On Thursday, 11 Aug 2022 at 14:39, Emmanuel Charpentier wrote:
> What about emacs' "custom" interface ? Do you use it ?

I do but generally only for user interface aspects, e.g. appearance and
interaction, and not for document specific aspects like exporting and
publishing.

-- 
: Eric S Fraga, with org release_9.5.4-720-g4db67d in Emacs 29.0.50