quarto-cli
jupytext
quarto-cli | jupytext | |
---|---|---|
8 | 20 | |
3,304 | 6,418 | |
3.5% | - | |
10.0 | 8.8 | |
6 days ago | about 1 month ago | |
JavaScript | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
quarto-cli
- FLaNK AI Weekly 18 March 2024
-
Quarto
Hello, I have a rather specific question.
I want to write a detailed tutorial (as HTML page) and a condensed version of it (as Reveal JS slides) from a single document.
I have found this suggestion[1] to specify the separate output file name for the slides in the header, and `quarto render myfile.qmd` will generate both.
Is there a way to include content (long form text, code, or images) that will only be exported in the HTML page but not in the slides (where space is more limited)?
[1] https://github.com/quarto-dev/quarto-cli/discussions/1751
-
Running Quarto Markdown in Docker
❯ docker build -t cavo789/quarto . [+] Building 208.2s (13/13) FINISHED docker:default => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2.08kB 0.0s => [internal] load metadata for docker.io/eddelbuettel/r2u:20.04 3.4s => CACHED [ 1/10] FROM docker.io/eddelbuettel/r2u:20.04@sha256:133b40653e0ad564d348f94ad72c753b97fb28941c072e69bb6e03c3b8d6c06e 0.0s => [ 2/10] RUN set -e -x && apt-get update && apt-get install -y --no-install-recommends pandoc pandoc-citeproc curl gdebi-core librsvg2-bin python3.8 47.6s => [ 3/10] RUN set -e -x && install.r shiny jsonlite ggplot2 htmltools remotes renv knitr rmarkdown quarto 27.2s => [ 4/10] RUN set -e -x && curl -o quarto-linux-amd64.deb -L https://github.com/quarto-dev/quarto-cli/releases/download/v1.4.529/quarto-1.4.529-linux-amd64.deb && gdebi - 12.1s => [ 5/10] RUN set -e -x && groupadd -g 1000 -o "quarto" && useradd -m -u 1000 -g 1000 -o -s /bin/bash "quarto" 0.5s => [ 6/10] RUN set -e -x && quarto install tool tinytex --update-path 23.0s => [ 7/10] RUN set -e -x && printf "\e[0;105m%s\e[0;0m\n" "Run tlmgr update" && ~/.TinyTeX/bin/x86_64-linux/tlmgr update --self --all && ~/.TinyTeX/bin/x86_64-linux/fm 77.9s => [ 8/10] RUN set -e -x && printf "\e[0;105m%s\e[0;0m\n" "Run tlmgr install for a few tinyText packages (needed for PDF conversion)" && ~/.TinyTeX/bin/x86_64-linux/tlmgr 11.7s => [ 9/10] RUN set -e -x && mkdir -p /input 0.5s => exporting to image 4.0s => => exporting layers 4.0s => => writing image sha256:fe1d20bd71a66eb574ba1f5b35c988ace57c2c30f93159caa4d5de2f8c490eb0 0.0s => => naming to docker.io/cavo789/quarto 0.0s What's Next? View summary of image vulnerabilities and recommendations → docker scout quickview
-
Quarto document rendered via quarto::quarto_render(): How to implement citations?
I had some trouble following this but I think what you're saying is the ` [@Bernhofer2021.02.23.432527]` tag isn't getting converted to the actual bib reference - is that right? I just copied this into my system and I could make that part work fine - using my own .bib file of course, and I used this csl which I copied locally. The one change I made to the setup was to put both the .bib and the .csl file in my working directory where the .qmd file is, and also as I commented on a different post of yours from the other day, I make sure there's no spaces in the path to my working directory (for either the folder names or the filenames). So for me, everything is in C:\Users\xxxx\workingdir - this is due to a known RStudio issue with spaces. Who knows if that's what you're running into or not.
-
Quarto: Mermaid rendering in word: code-execution halts after format is generated, waiting indefinitely for a chrome-process to close
You should ask in the Quarto discussion group on their GitHub. They are extremely reactive if you can give a MWE.
- quarto-cli: Open-source scientific and technical publishing system built on Pandoc.
- The Jupyter+Git problem is now solved
jupytext
- The Jupyter+Git problem is now solved
-
Do you git commit jupyter notebooks?
Jupytext (https://github.com/mwouts/jupytext) has been designed exactly for this
-
The hatred towards jupyter notebooks
jupytext is your friend.
-
Edit notebooks in Google cloud
So if you run your own jupyter server, -jupy+text can be a great workflow : it takes your notebook synchronized with other formats (python file, makdown, ...), so you can edit your py/md file with neovim, and refresh the browser to execute the notebook.
-
Rant: Jupyter notebooks are trash.
Automatically convert ipynb files to py when saving them on JupyterLab
-
Two questions regarding working with jupyter notebooks (git, vim)
I don't use Jupyter so I don't know for sure, but on a quick glance you might want to look at https://github.com/mwouts/jupytext to see if that could help at all.
-
JupyterLite is a JupyterLab distribution that runs in the browser
The format is only partially invented, it follows Jupytext [0], but adds support for cell metadata. There is no obvious way to get that in fenced codeblocks, especially with the ability to spread it over multiple lines so it plays well with version control.
One more consideration is that it's not "Markdown with code blocks interspersed", one might as well use plaintext or AsciiDoc.
Of course there are tradeoffs.. I wish I had more time to work on it.
[0]: https://github.com/gzuidhof/starboard-notebook/blob/master/d...
[1]: https://github.com/mwouts/jupytext
-
Many write research papers in R Markdown - What is the alternative setup in Python?
Using jupytext (allows you to open .md files as notebooks) + jupyter gives you pretty much the same experience. The main issue is that the cell's output will be discarded. To fix it, you can use ploomber to generate an output HTML, so the workflow goes like this:
-
Jupyter Notebooks.
First, the format. The ipynb format does not play nicely with git since it stores the cell's source code and output in the same file. But Jupyter has built-in mechanisms to allow other formats to look like notebooks. For example, here's a library that allows you to store notebooks on a postgres database (I know this isn't practical, but it's a great example). To give more practical advice, jupytext allows you to open .py files as notebooks. So you can develop interactively but in the backend, you're storing .py files.
What are some alternatives?
jupyter-book - Create beautiful, publication-quality books and documents from computational content.
jupyter - An interface to communicate with Jupyter kernels.
ipyflow - A reactive Python kernel for Jupyter notebooks.
rmarkdown - Dynamic Documents for R
Pluto.jl - 🎈 Simple reactive notebooks for Julia
sagemaker-run-notebook - Tools to run Jupyter notebooks as jobs in Amazon SageMaker - ad hoc, on a schedule, or in response to events
jupyterlab-git - A Git extension for JupyterLab
nbdev - Create delightful software with Jupyter Notebooks
github-orgmode-tests - This is a test project where you can explore how github interprets Org-mode files
papermill - 📚 Parameterize, execute, and analyze notebooks
nbdime - Tools for diffing and merging of Jupyter notebooks.