You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I consider myself a minimalist and like the idea of litedown. However, one thing that prevents me from trying litedown more is its focus on users who primarily work within an R session. Indeed, the docs seem to even assume users are using RStudio and frequently talk about the knit button.
I would try litedown more if it could (i) offer a CLI tool or (ii) provide guidance in the docs on how to create a bash wrapper around RScript to use it.
Method (ii) may be easy and straightforward (am i right?).
But knowing that the developer has users like me in mind would certainly encourage me to try litedown more.
I think there are other potential users like me. While litedown is an R package, its main functions are more similar to pandoc/quarto. I think most people use pandoc and quarto from CLI.
The text was updated successfully, but these errors were encountered:
R -e 'litedown::roam(open=TRUE);while(TRUE)Sys.sleep(.01)'# Ctrl + C to stop
If you only intend to render one file, call litedown::fuse() or litedown::mark(), which can also be done via R -e, or a shell script wrapper, which should be quite straightforward to write, e.g., fuse.sh
If you are looking for a product similar to litedown but doesn't depend on R, you may come back a year later. I have had some wild ideas for quite a while and need to find time to try.
YAML header should contain all the information and I usually have a project-wide makefile, but an executable script added to a path so I could just do:
Yes, that would be nice and shouldn't be hard to write (especially on *nix).
A true executable?
When I said "a year" above, I meant "give me some time next year to learn Rust and reimagine Jupyter" (then a by-product would be a true CLI tool, not just a wrapper shell script).
I consider myself a minimalist and like the idea of litedown. However, one thing that prevents me from trying litedown more is its focus on users who primarily work within an R session. Indeed, the docs seem to even assume users are using RStudio and frequently talk about the knit button.
I would try litedown more if it could (i) offer a CLI tool or (ii) provide guidance in the docs on how to create a bash wrapper around RScript to use it.
Method (ii) may be easy and straightforward (am i right?).
But knowing that the developer has users like me in mind would certainly encourage me to try litedown more.
I think there are other potential users like me. While litedown is an R package, its main functions are more similar to pandoc/quarto. I think most people use pandoc and quarto from CLI.
The text was updated successfully, but these errors were encountered: