carbonate VS silicon

I see folks wondering about the use case - so here's one: I created a Github Action for use in Github Actions. The benefits:

- Easy to view and understand the image of the code v/s the code block text when using a mobile device. Why? Easier to scroll images v/s text.

- Members will no longer have to rely on the issue reporters and commenters to format their code blocks correctly. Using the in built formatter, the code is always structured properly

- Maintainers can style the code blocks to suit their project's language and guidelines and not put the onus of this on the issue reporter / commenter

Reference: https://github.com/callmekatootie/carbonate

I used Carbon to generate the images in this case - but you get the gist of what one can use images of code for

There is silicon.nvim that uses the cli tool silicon to export the code as an image (I think there is also an alternative that uses carbon). There is also vim-copy-as-rtf that works only on OSx and Code2RTF.vim that works only on Windows (there was a fork of vim-copy-as-rtf for Linux, but I can't find it). Finally, there is this discussion about alternatives, being one of them to use pandoc and :TOHtml to export the text as RTF

Use Carbon or if you want a program there is silicon

Have you seen https://github.com/Aloxaf/silicon by the way?

Another one in Rust: https://github.com/Aloxaf/silicon

You can use https://carbon.now.sh/ for this!Find the CLI here: https://github.com/mixn/carbon-now-cliAlternative: Silicon (Rust): https://github.com/Aloxaf/silicon

You can follow directions here on how to install it on your system.

Silicon (CLI)