see - See a cute cat.
cat you see!? Its a fancy cat! :cat:
[!WARNING]
DISCLAIMER: This project is currently in alpha stage. It may contain bugs, incomplete features, or undergo significant changes. Use with caution and please report any issues you encounter.
see is a tool that functions as both a minimalistic Markdown renderer and a code viewer for the terminal. It provides syntax highlighting, emoji support, and image rendering capabilities, offering a visually appealing way to view both Markdown content and various code files directly in your console.
Motivation
The primary goal of see is to create a unified tool for viewing both CLI documentation in Markdown and code files, renderable in both the terminal and web browse:rs. This approach aims to:
Provide a unified documentation and code viewing format accessible across different environments Enable quick viewing and editing of CLI documentation and code files from anywhere Make your CLI experience more visually appealing and informative
As the project evolved from its initial focus on Markdown, support for viewing code files was added, expanding its utility in diverse development ecosystems. Now, see is your go-to tool for seeing everything that a cat can see!
Features
- Minimalistic rich markdown rendering in the terminal
- State-of-the-art code viewing capabilities with superior syntax highlighting for a wide range of programming languages, powered by tree-sitter
- More accurate, context-aware syntax highlighting
- Emoji support :smile:
- Image rendering (when possible)
- Clickable links (in supported terminals)
- Table formatting
- Blockquote styling
- And more adding soon!
Installation
There are several ways to install see:
1. Install prebuilt binaries via shell script (Recommended)
The easiest and fastest way to install see is by using our shell script:
|
DISCLAIMER: The version number in the URL above (v0.2.10) may not be the latest version. Please check the releases page for the most recent version and update the URL accordingly before running the command.
2. Using prebuilt binaries from GitHub releases
If you prefer to manually download and install the binary:
- Visit the see releases page on GitHub.
- Find the latest release version.
- Download the appropriate binary for your operating system and architecture.
- Extract the downloaded file if necessary.
- Move the
seebinary to a directory in your system's PATH (e.g.,/usr/local/binon Unix-like systems).
3. Install prebuilt binaries via Homebrew
If you're using Homebrew, you can install see with:
4. Using Cargo
You can install see directly from crates.io using Cargo:
This will download, compile, and install the latest version of see. Make sure your Rust installation is up to date.
5. Building from Source
If you prefer to build from source or want to contribute to the project:
-
Ensure you have Rust and Cargo installed. If not, get them from https://rustup.rs/.
-
Clone the repository:
-
Build and install the project using Cargo:
This will compile the project and install the see binary in your Cargo bin directory, which should be in your PATH.
Usage
There are two main ways to use see:
1. Rendering a Markdown file
To render a Markdown file, simply pass the path to the file as an argument:
2. Rendering Markdown from piped input
see can also read Markdown content from standard input, allowing you to pipe content directly into it:
|
This feature is particularly useful for integrating see with other commands or for quickly rendering Markdown snippets. For example:
| |
Integration with CLI Tools
see can be easily integrated with CLI tools to replace traditional man pages with rich Markdown documentation. Here's an example of how you can use see with a custom CLI tool's --help flag:
#!/bin/bash
# Name: mycli
# Description: Example CLI tool using see for documentation
if ; then
# Use see to render the Markdown help file
else
# Regular CLI functionality
fi
In this example, create a Markdown file at ~/.mycli/help.md with your CLI documentation. When users run mycli --help, they'll see a beautifully rendered version of your Markdown documentation instead of a plain text man page.
This approach allows you to maintain a single source of documentation that's readable in raw form, rendered nicely in the terminal, and viewable in web browsers.
Viewing see's Own Documentation
see uses itself to display its own documentation. You can view see's documentation directly in your terminal by running:
This command will render see's main documentation file /docs, giving you a practical example of see in action and providing detailed information about its usage and features.
see as a Code Viewer (Experimental)
In addition to rendering Markdown, see serves as a powerful code viewer for the terminal. It provides an efficient way to review code directly in your console with advanced syntax highlighting powered by tree-sitter which gives more accurate, context-aware syntax highlighting,
Usage:
Configuration
see supports user-defined configuration files. You can customize various aspects of the rendering process by creating a config.toml file in the following location:
- On Linux and macOS:
~/.config/see/config.toml - On Windows:
C:\Users\<USERNAME>\AppData\Roaming\see\config.toml
You can generate a default configuration file by running:
Here's an example of what you can configure:
= 40
= 13
= true
= true
= false
= true
max_image_widthandmax_image_height: Maximum dimensions for rendered imagesrender_images: If false, images will not be renderedrender_links: If false, links will not be clickablerender_table_borders: If true, tables will be rendered with ASCII borders (default: false)show_line_numbers: If true, line numbers will be shown for code files (can also be set with--line-numbersoption)
Note: see uses tree-sitter thanks to inkjet for syntax highlighting. Currently, only one theme is implemented, but there are plans to make see compatible with Helix editor themes in the future, which will greatly expand customization options.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request. As this project is in alpha, your input and contributions can significantly shape its development.
Known Issues
As this is an alpha version, you may encounter bugs or incomplete features. Some known limitations include:
License
This project is licensed under the MIT License. See the LICENSE file for details.
TODO:
-
Extended Markdown Support
-
Improve syntax highlighting
-
Theming and Customization: Develop user-customizable color schemes and rendering options