yarstu, another rich terminal screenshot utility
Find a file
2023-05-07 23:38:38 -05:00
assets docs: add updated preview/svgs 2022-06-18 16:55:57 -05:00
docs docs: add reference to deviation from rich 2022-06-18 17:09:10 -05:00
scripts docs: add reference to deviation from rich 2022-06-18 17:09:10 -05:00
yartsu fix: update for newer versions of rich 2023-05-07 23:38:38 -05:00
.flake8 feat: patch console to improve drop-shadow 2022-06-18 16:52:48 -05:00
.gitignore chore: update pdm lock 2023-05-07 23:38:38 -05:00
.pre-commit-config.yaml build: change pre-commit config 2023-05-07 23:34:55 -05:00
.task.cfg.mk chore: switch to .task.cfg.mk 2023-04-26 17:26:31 -05:00
LICENSE.txt feat: switch default font to support nerd fonts 2022-06-15 01:40:22 -05:00
Makefile chore: switch to .task.cfg.mk 2023-04-26 17:26:31 -05:00
pdm.lock chore: update pdm lock 2023-05-07 23:38:38 -05:00
pyoxidizer.bzl build: switch build framework to pyoxidizer 2022-06-16 01:19:48 -05:00
pyproject.toml chore: update pdm lock 2023-05-07 23:38:38 -05:00
README.md docs: update todo 2022-06-19 15:28:37 -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 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

pip install yartsu

There is a standalone binary available for linux in the releases.

Optionally install with eget:

eget daylinmorgan/yartsu

Otherwise you can download an extract manually to somewhere on your path.

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

Supported Characters

Currently yartsu loads the nerd font patched FiraCode font. This should result in general support for emoji's and nerd font icons.

Logo

Note: github won't load the font's when displaying on the README. Click on the svg to see the nerd font icons.

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.

TODO (for stable release)

  • add support for nerd-fonts
  • add optional shadow
  • add unit tests
  • setup CI for release/testing