-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
glow not rendering heading levels other than top-level #646
Comments
They are being recognized and rendered. specifically, what is the expected formatting? |
I suppose I was expecting no Heading 1 is highlighted as I would expect, but the rest are all the same color and show the hashes (I guess to indicate the level ?) I understand that just color/bold would be nice but wouldn't actually indicate the Heading level. Maybe include the |
This is correct, h1 is the only different one because it should be the most eye-catching, the hash symbol is still present at the other levels to indicate which level that header is, given that they have the same color. |
Personally I would like colors/bolding, but keep the Heh, if you do decide to add this, perhaps make it configurable. What looks nice in one terminal color scheme (solarized_dark) might be eye-stabbing in another :P |
FYI it is configurable: https://github.com/charmbracelet/glamour/tree/master/styles The Catppuccin theme supports different colors per header. |
Yeah, hence keeping the |
Describe the bug
glow does not seem to render headings other than top-level
# Heading 1
. Other levels like## Heading 2
render in a color, but also show the##
Setup
Source Code
Simple
test.md
Expected behavior
The sample
test.md
should render appropriately.# Heading 1
renders as expected, with coloring/bold/etc.## Heading 2
and the others only render in blue and show the heading level hashesThis may well be an unintended and unexpected confluence of factors like font, terminal etc.
Screenshots
Additional context
Using the "Hack Nerd Font" for alacritty and gnome-terminal
The text was updated successfully, but these errors were encountered: