Automatically change file names by output format, using qmd filename?

[DBecker7]

I would like to produce lecture slides in beamer pdf, while also creating a basic pdf file with extra information in :::notes::: containers. Both pdf and beamer produce files with the same name, so the slides get overwritten.

Is there something like:

format:
  pdf:
    output: "[$filename]_notes.pdf"
  beamer:
    output: "[$filename]_slides.pdf"

I will be doing this for 20+ lectures each for two courses, so anything that reduces manual metadata entry is a plus (I am doing this within a quarto project).

[mcanouil]

The YAML option output does not exist.
What you want is output-file which is described in "reference" pages of the formats, see https://quarto.org/docs/reference/formats/pdf.html#rendering and https://quarto.org/docs/reference/formats/presentations/beamer.html#rendering.

Note that you can pass shortcode variable into output-file allowing you to use the env or meta shortcodes, see https://quarto.org/docs/authoring/variables.html.
This does not work, because I believe shortcodes are evaluated too late.

[DBecker7]

Thanks for continuing to help me!

Content of move-beamer.sh (quarto project directory):

echo "Running move_beamer..sh"
pwd

for f in *.pdf;
    mv $f ../Slides;
done

echo "I moved from this directory" > tmp.txt

Content of _quarto.yml:

format: 
    beamer:
        theme: Madrid
        colortheme: spruce
        aspectratio: 169
        toc: false
        post-render: move_beamer.sh
        execute:
            echo: false
            fig-width: 7
            fig-height: 3.5
    pdf:
        toc: true
        execute:
            echo: true
            fig-width: 8
            fig-height: 5

[DBecker7]

I updated quarto to the latest version and now the error when I use latex-output-dir is more informative. It's looking for the .tex file in the quarto project directory, but it's in the directory specified by latex-output-dir.

Both quarto render --to pdf as well as quarto render --to beamer run without error when using latex-output-dir.

[DBecker7]

Another update: ~~I have got the latex-output-dir strategy working. For whatever reason, the second block needs keep-tex: true in order for this to work. I've switched the pdf and beamer blocks and it doesn't matter the order as long as the second block has keep-tex: true. Also note that the .tex files aren't actually saved unless both blocks have keep-tex. ~~

... never mind. I thought it was working, but it's actually making the same thing twice (either two copies of the pdf or two copies of the beamer pres, whichever block comes second).

[DBecker7]

For testing purposes, I have created a MWE here: https://github.com/DBecker7/quarto_dual_latex_outputs

[cderv]

@DBecker7 Regarding post-render this is a project option (https://quarto.org/docs/reference/projects/options.html) part of the project scripts feature (https://quarto.org/docs/projects/scripts.html)
If you put them under format, this will not work. I am suprised that YAML validation does not help know better on this 🤔
you should not get autocompletion for this option though when in VSCODE or RStudio IDE.

Regarding the rest, thanks a lot for your reprex repo. We'll look into that ! I do think some of this is part of an existing issue we'll look at for 1.4 #2596

Maybe you can confirm or add to that ?

[DBecker7]

No, I did not get autocomplete for those options, so it makes sense (autocomplete sometimes doesn't work for me, especially with multiple editor windows open, so I didn't think twice about that). So post-render probably wouldn't work for this use case, then? Yes, I think some of the workings of latex-output-dir are at fault for some of my errors, especially the ones regarding the location of the text file! Thanks for all your time and help! For now I don't seem to have any way to change file name or path based on render format, so for now I'll just do them manually with the cli.

…

On Fri, Apr 21, 2023, 4:55 PM Christophe Dervieux ***@***.***> wrote: @DBecker7 <https://github.com/DBecker7> Regarding post-render this is a project option (https://quarto.org/docs/reference/projects/options.html) part of the project scripts feature ( https://quarto.org/docs/projects/scripts.html) If you put them under format, this will not work. I am suprised that YAML validation does not help know better on this 🤔 you should not get autocompletion for this option though when in VSCODE or RStudio IDE. Regarding the rest, thanks a lot for your reprex repo. We'll look into that ! I do think some of this is part of an existing issue we'll look at for 1.4 #2596 <#2596> Maybe you can confirm or add to that ? — Reply to this email directly, view it on GitHub <#5261 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYCHM4RFI5SZSSZWP47CTLXCLX3PANCNFSM6AAAAAAXGWDYEU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mcanouil]

Project options are defined in _quarto.yml as documented in https://quarto.org/docs/projects/scripts.html#pre-and-post-render¹.

project:
  post-render:

Footnotes

1. singleton documents are not Quarto project, so based on your example setup, it won't work, maybe there is an enhancement here. ↩

[mcanouil]

Your bash/shell script is not valid by the way.

#!/usr/bin/env bash

echo "Running move_beamer..sh"
pwd

for f in *.pdf;
do
    mv -f $f Slides;
done

echo "I moved from this directory" > tmp.txt

[baptiste]

I think you could use project profiles: one for slides, one for notes. Either specifying the output-dir differently for each, or a separate post-render script for each.

I've forked your example and it seems to work

[mcanouil]

Indeed, based on the example repository, project profiles (see https://quarto.org/docs/projects/profiles.html#profile-configuration) should be the way to go here.

[DBecker7]

Thank you, this is probably the best way to go.

My hope was for these class notes to be shared with others who may not be familiar with quarto (either by using keep-tex or converting them all to Rmd or ipynb, depending on the next professor), so I'll just stick to rendering twice for now. It's very unfortunate that this use-case can't work the same as, say, making a pdf and an html (where quarto render once will do both and have both output files remain in the folder).