ZH version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
83% Positive
Analyzed from 452 words in the discussion.
Trending Topics
#glow#editor#markdown#project#https#github#terminal#features#com#feedback
Discussion (22 Comments)Read Original on HackerNews
> <bullet> <checkbox> description 1
> <bullet> <checkbox> description 2
> ...
Like... why are we doing this. What is the purpose of having a bunch of green checkbox emojis in the already bulleted list of features. The only thing it tells me is that an LLM was probably used extensively in building this project.
`cargo audit` finds 3 vulnerabilities, you should fix them.
Blazing safe.
https://github.com/charmbracelet/glow
https://github.com/bahdotsh/mdterm
I built leaf, a Markdown previewer that runs entirely in the terminal.
It supports keyboard/mouse navigation, syntax highlighting, tables, checkboxes, clickable links, search, table of contents, local Markdown links, inline images, Mermaid diagrams, and LaTeX-to-Unicode rendering.
It works on Linux, macOS, Windows, and Termux.
GitHub: https://github.com/RivoLink/leaf
I’d appreciate feedback on the UX, missing features, and performance on large Markdown files.
Also maybe a single paragraph at the top describing the project rather than jumping into `install`.
Do you have a specific use case?
It seems to me that markdown is for writing with the ultimate output supposedly being html. Having a viewer of the markdown doesn't seem to add anything.
Whereas making it an editor makes it more of a rich text editor.
I'm not particularly saying youre wrong, more posing a philosophical question.
The idea is not to replace an editor, but to complement it: - "open in editor" lets you edit the file with your preferred editor - "watch" automatically refreshes the preview when the file changes
So you can keep your usual workflow while having a fast, structured preview directly in the terminal.