This looks neat, congrats.
For anyone looking for a more general renderer, https://github.com/charmbracelet/glow.
In Show HN: Beautiful Markdown rendering in your terminalcharmbracelet
glow
Go2019–2026
charmbracelet / glow
glow
Render markdown on the CLI, with pizzazz! 💅🏻
34Distinct people
43Mentions
0Explicit recommenders
28KGitHub stars
What to know before exploring
What it is
Render markdown on the CLI, with pizzazz! 💅🏻
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- aider-ai/aider · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year43 dated mentions
Observed mentions: 2019-12-27 22:32:19 UTC to 2026-09-11 12:50:29 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 9 | 1 | 8 |
From the project README
An excerpt from the repository, fetched Nov 12, 2026.
Read the project’s introduction
Glow
Render markdown on the CLI, with pizzazz!
What is it?
Glow is a terminal based markdown reader designed from the ground up to bring
out the beauty—and power—of the CLI.
Use it to discover markdown files, read documentation directly on the command
line. Glow will find local markdown files in subdirectories or a local
Git repository.
Installation
Package Manager
# macOS or Linux
brew install glow
# macOS (with MacPorts)
sudo port install glow
# Arch Linux (btw)
pacman -S glow
# Void Linux
xbps-install -S glow
# Nix shell
nix-shell -p glow --command glow
# FreeBSD
pkg install glow
# Solus
eopkg install glow
# Windows (with Chocolatey, Scoop, or Winget)
choco install glow
scoop install glow
winget install charmbracelet.glow
# Android (with termux)
pkg install glow
# Ubuntu (Snapcraft)
sudo snap install glow
# Debian/Ubuntu
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg
echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list
sudo apt update && sudo apt install glow
# Fedora/RHEL
echo '[charm]
name=Charm
baseurl=https://repo.charm.sh/yum/
enabled=1
gpgcheck=1
gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo
sudo yum install glow
Or download a binary from the releases page. MacOS, Linux, Windows,
FreeBSD and OpenBSD binaries are available, as well as Debian, RPM, and Alpine
packages. ARM builds are also available for macOS, Linux, FreeBSD and OpenBSD.
Go
Or just install it with go:
go install charm.land/glow/v3@latest
Build (requires Go 1.21+)
git clone https://github.com/charmbracelet/glow.git
cd glow
go build
The TUI
Simply run glow without arguments to start the textual user interface and
browse local. Glow will find local markdown files in the
current directory and below or, if you’re in a Git repository, Glow will search
the repo.
Markdown files can be read with Glow's high-performance pager. Most of the
keystrokes you know from less are the same, but you can press ? to list
the hotkeys.
The CLI
In addition to a TUI, Glow has a CLI for working with Markdown. To format a
document use a markdown source as the primary argument:
# Read from file
glow README.md
# Read from stdin
echo "[Glow](https://github.com/charmbracelet/glow)" | glow -
# Fetch README from GitHub / GitLab
glow github.com/charmbracelet/glow
# Fetch markdown from HTTP
glow https://host.tld/file.md
Word Wrapping
The -w flag lets you set a maximum width at which the output will be wrapped:
glow -w 60
Paging
CLI output can be displayed in your preferred pager with the -p flag. This defaults
to the ANSI-aware less -r if $PAGER is not explicitly set.
Styles
You can choose a style with the -s flag. When no flag is provided glow tries
to detect your terminal's current background color and automatically picks
either the dark or the light style for you.
glow -s [dark|light]
Alternatively you can also supply a custom JSON stylesheet:
glow -s mystyle.json
For additional usage details see:
glow --help
Check out the Glamour Style Section
to find more styles. Or make your own!
The Config File
If you find yourself supplying the same flags to glow all the time, it's
probably a good idea to create a config file. Run glow config, which will open
it in your favorite $EDITOR. Alternatively you can manually put a file named
glow.yml in the default config path of you platform. If you're not sure where
that is, please refer to glow --help.
Here's an example config:
# style name or JSON path (default "auto")
style: "light"
# mouse wheel support (TUI-mode only)
mouse: true
# use pager to display markdown
pager: true
# at which column should we word wrap?
width: 80
# show all files, including hidden and ignored.
all: false
# show line numbers (TUI-mode only)
showLineNumbers: false
# preserve newlines in the output
preserveNewLines: false
Contributing
See contributing.
Feedback
We’d love to hear your thoughts on this project. Feel free to drop us a note!
Twitter
The Fediverse
Discord
License
MIT
Part of Charm.
Charm热爱开源 • Charm loves open source
Read the full README on GitHubWhat Hacker News says
43 sourcesI assume from the name that Shine is inspired by [Glow](https://github.com/charmbracelet/glow), how is this different?
In Show HN: Shine – a terminal Markdown previewer and docs linterslop, attemped AEO?
It reads like there are not dozens of these already. Charm's stack even support stylesheets
https://github.com/charmbracelet/glow (CLI)
https://github.com/charmbracelet/glamour (module)
In Leaf Makes Markdown Readable Inside the Terminalor just use glow which is golang.
https://github.com/charmbracelet/glow
In Show HN: leaf – a terminal Markdown previewer with a GUI-like experiencecool project, how does it compare to glow? https://github.com/charmbracelet/glow
In Show HN: leaf – a terminal Markdown previewer with a GUI-like experienceGlow: Render Markdown on the CLI, with Pizzazz
2 points · Open discussionHere's the one I use a lot ... And the underlying `glamour` library is great for programmatic markdown display: https://github.com/charmbracelet/glow.
In Markdown CLI viewer with VI keybindingsGlow is pretty great and has been around for a while:
https://github.com/charmbracelet/glow
In Markdown CLI viewer with VI keybindingsOh I see what you mean about glow, that looks like a nice UX improvement - I'm going to try your fork.
https://github.com/charmbracelet/glow/compare/master...fragm...
In Assorted less(1) tipsIf you're looking for a CLI markdown reader then I'd recommend glow.
https://github.com/charmbracelet/glow
In Plugins case study: mdBook preprocessorsI guess I don't see those as big downsides because I don't think people usually want binary data or quoted strings back from a CLI command, nor do they want column oriented output, nor "user friendly" tables.
Answering --help with JSON is a good example, how bad is it really if the response is JSON? Well, using less works fine still and you can still grep if you want simple substring search. Wanting a section is probably more common, so maybe you'd "grep" for a subcommand with `jq .subcommand` or an option with `jq .subcommand.option`, and maybe get yourself a fancier, JSON-friendly version of less that handles escaped quotes and newlines. Tables and tab-or-space delimited output overflow char limits, force the command-generator to figure out character wrapping, and so on. Now you need a library to generate CLI help properly, but if y
Read the rest
ou're going to have a library why not just spit JSON and decouple completely from display details to let the consumer handle it.
Structured output by default just makes sense for practically everything except `cat`. And while your markdown files or csv files might have quoted strings, looking at the raw files isn't something people really want from shells or editors.. they want something "rendered" in one way or another, for example with syntax highlighting.
Basically in 2025 neither humans nor machines benefit much from unstructured raw output. Almost any CLI that does this needs to be paired with a parser (like https://github.com/kellyjonbrazil/jc) and/or a renderer (like https://github.com/charmbracelet/glow). If no such pairing is available then it pushes many people to separately reinvent parsers badly. JSON's not perfect but (non-minified) it's human-readable enough to address the basic issues here without jumping all the way towards binary or (shudder) HTML
Charmbracelet/glow: Render Markdown on the CLI, with pizzazz
6 points · Open discussionShow HN: Doxx – Terminal .docx viewer inspired by Glow
I got tired of open file.docx → wait 8 seconds → close Word just to read a document, so I built a terminal-native Word viewer!
What it does:
* View `.docx` files directly in your terminal with (mostly) proper formatting
* Tables actually look like tables (with Unicode borders!)
* Nested lists work correctly with indentation
* Full-text search with highlighting
* Copy content straight to clipboard with `c`
* Export to markdown/CSV/JSON
Why I made this:
Working on servers over SSH, I constantly hit Word docs I needed to check quickly. The existing solutions I'm aware of either strip all formatting (docx2txt) or require GUI apps. Wanted something that felt as polished as [glow](https://github.com/charmbracelet/glow) but for Word documents.
The good stuff:
* 50ms startup vs Word's 8+ seconds
* Works over SSH (obviously)
* Preserves document s
Read the rest
tructure and formatting
* Smart table alignment based on data types
* Interactive outline view for long docs
Built with Rust + ratatui and heavily inspired by Charm's [glow](https://github.com/charmbracelet/glow) package for viewing Markdown in the CLI (built in Go)!
# Install
cargo install --git https://github.com/bgreenwell/doxx
# Use
doxx quarterly-report.docx
Still early but handles most Word docs I throw at it. Always wanted a proper Word viewer in my terminal toolkit alongside `bat`, `glow`, and friends. Let me know what you think!
Show HN: Split Vim Markdown Preview – Terminal-Based Markdown Preview for Vim
I built this lightweight Vim plugin for developers who want to preview markdown without leaving their terminal environment. It uses https://github.com/charmbracelet/glow to render beautiful markdown directly in a Vim split window.
Key features:
- Toggle preview with \mp - no need to leave Vim
- Beautiful terminal-based rendering with syntax highlighting
- Handles code blocks (200+ languages), tables, math equations, and task lists
- Split window layout keeps your workflow intact by toggling with \mp
Why I built this: I love using vim to quickly edit files, write down thoughts, and update notes. Building terminal tools can sometimes be big time commitments that take me away from other work. Claude Code helped me to quickly vibe code this integration to improve my workflow.
When I looked at other markdown plugins for vim, the
Read the rest
y required preview plugins requiring Node servers and browser switching, which breaks concentration when writing documentation. This keeps everything in the terminal where Vim users prefer to work, so they can stay in flow while building.
The repo includes a demo GIF showing the plugin in action so you can see how it looks before installing. Installation is straightforward - just install glow and drop the plugin file in your Vim directory.
glow is kinda that: https://github.com/charmbracelet/glow
In Show HN: Chawan TUI web browserShowing the 15 most recent of 43 sources. Enable JavaScript to search and browse every indexed mention.