yarstu, another rich terminal screenshot utility
Find a file
2022-06-15 01:07:56 -05:00
assets second commit 2022-06-14 18:46:20 -05:00
docs second commit 2022-06-14 18:46:20 -05:00
scripts build: move preamble script to scripts/ 2022-06-15 00:54:07 -05:00
yartsu second commit 2022-06-14 18:46:20 -05:00
.flake8 second commit 2022-06-14 18:46:20 -05:00
.gitignore second commit 2022-06-14 18:46:20 -05:00
.pre-commit-config.yaml second commit 2022-06-14 18:46:20 -05:00
LICENSE.txt chore: add license 2022-06-14 23:06:13 -05:00
Makefile build: move preamble script to scripts/ 2022-06-15 00:54:07 -05:00
pdm.lock second commit 2022-06-14 18:46:20 -05:00
pyproject.toml chore: add urls to project table 2022-06-15 00:57:19 -05:00
README.md docs: update version 2022-06-15 01:07:56 -05:00

YARTSU

Logo

yartsu, another rich terminal screenshot utility


Stargazers Issues MIT License

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 programatically 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 ouptut outside of rich/python. Hopefully, you find it useful.

If you come across anything unexpected please submit an issue.

Install

pip install yartsu

You can also install the shiv based zipapp from the releases page.

With cURL:

curl -o ~/bin/yartsu -fL https://github.com/daylinmorgan/yartsu/releases/download/v22.06-beta1/yartsu
chmod u+x ~/bin/yartsu

With eget:

eget daylinmorgan/yartsu

Usage

Logo

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 seperate 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

TODO

  • add unit tests
  • add support for nerd-fonts
  • add optional shadow
  • add more themes