| .github/workflows | ||
| assets | ||
| docs | ||
| scripts | ||
| src/yartsu | ||
| .flake8 | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .task.cfg.mk | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| pdm.lock | ||
| pyoxidizer.bzl | ||
| pyproject.toml | ||
| README.md | ||
| todo.md | ||
Yartsu
NOTE: this is a currently in a beta release and the API is subject to change (feedback welcome)
Inspired by recent commits in the wonderful library rich I decided to write yartsu.
I needed to programmatically generate screenshots for documentation purposes. The new export_svg methods in rich were a godsend.
So I wanted to try to make this feature a little more generalizable to program output outside of rich/python.
Hopefully, you find it useful.
If you come across anything unexpected please submit an issue.
Install
pipx install yartsu
# OR
pip install yartsu
Releases
There is a standalone binary available for linux in the releases (Support for additional platforms is planned).
Optionally install with eget:
eget daylinmorgan/yartsu
Otherwise you can download an extract manually to somewhere on your path.
Usage
Getting a properly formatted output from a terminal screenshot is challenging.
There are three options for generating a screenshot.
If one of the below option causes you any headaches consider first trying a different option.
Option 1: Pipes
Many tools that color output (i.e. grep or ls) additionally allow
you to force ANSI color codes to be included even when piping output.
In these cases you can simply pipe the output directly into yartsu
ls --color=always | yartsu -w 50 -o assets/ls_color.svg
Option 2: Subprocess/Pty
With this option yartsu will deploy a subprocess and pty
to run your command for you in an attempt to preserve ANSI.
Note with this option you need to separate
the command you want to run with yartsu args using --.
yartsu -w 50 -o assets/ls_color.svg -- ls --color /
Option 3: Text File
Finally, if you neither of the above options work and you can
manage to preserve the codes in a plain text file you can pass this as input to yartsu.
ls --color > ls.txt
yartsu -w 50 -i ls.txt -o assets/ls_color.svg
By default svgs will be saved at ./capture.svg.
Additionally, for options 1 and 3 you may want to define your own title with -t/--title.
For option 2 the title will by default be the cmd ran by yartsu.
Themes
There are a number of themes you can use to style output.
Use yartsu --list-themes to see the available options.
Then you can specify the theme you want with --theme, i.e. yartsu --theme rich_default.
You may also use the environment variable YARTSU_THEME.
See here a preview of the available themes
Differences from Rich
For both practical and stylistic reasons the underlying code used to generate the SVG is slightly different than rich's default save_svg method. See here for the current deviation between the latest releases of each respective release.