--setup does not work

[jemabaris]

I just installed mdfried via yay because I was interested in the implementation of the kitty text sizing protocol. Headings do in fact get rendered in different sizes but something looks off with the font and with the spacing of characters. But for whatever reason I never had the setup run upon the first time opening mdfried. Using the -s or --setup flags later also does not work. There is also no config file being created under ~/.config/mdfried/

This is with the latest version 0.19.2 under Arch Linux.

If I can provide any further information you need for debugging please let me know :)

All the best

Janis

[benjajaja]

Setup is meant for "font setup" when text-sizing-protocol is not available. For kitty, the font should just work. There may be spacing issues though, because the protocol requires some gymnastics with width/size. Maybe I misunderstood something, but mdfried groups characters which could cause weird spacing in unexpected places. Please do report what exactly looks off 😀 I will also make `--setup` print an explicit message when im kitty. Benjamin Große

…

On Tue, 14 Apr 2026, 00:48 jemabaris, ***@***.***> wrote: *jemabaris* created an issue (benjajaja/mdfried#92) <#92> I just installed mdfried via yay because I was interested in the implementation of the kitty text sizing protocol. Headings do in fact get rendered in different sizes but something looks off with the font and with the spacing of characters. But for whatever reason I never had the setup run upon the first time opening mdfried. Using the -s or --setup flags later also does not work. There is also no config file being created under ~/.config/mdfried/ This is with the latest version 0.19.2 under Arch Linux. If I can provide any further information you need for debugging please let me know :) All the best Janis — Reply to this email directly, view it on GitHub <#92>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACLXR44JGRUETHHGW47HT34VVVC7AVCNFSM6AAAAACXYBGU2CVHI2DSMVQWIX3LMV43ASLTON2WKOZUGI2TQMZTGM3DEMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jemabaris]

Thanks for the fast reply! No you understood everything right, I just didn't know that the font selection thing wasn't needed when using kitty. I will attach a screenshot where you can see some of the spacing issues.
Like with: "Gettin g Star ted" where it's especially noticeable. Are there any plans to support the kitty graphics protocol for inline image rendering in the future btw? I am looking for a decent solution for rendering markdown files as similar as possible to Obsidian.md in a TUI. So far I've either found CLI tools that do one or the other, but non that support all the protocols we have available with kitty nowadays.

P.S.
Looking at the 'scharfes S' in your name I might add - Liebe Gruesse aus der Naehe von Muenchen :)

[jemabaris]

Lol, looking at my own screenshot I just realized that there actually is inline image rendering but for whatever reason it's only rendering one of about five images or so that should be in the markdown file. I was clearly blind before^^

[benjajaja]

Yea kitty is supported, but there's no way to force it for the headers IIRC. Thanks for the screenshot. Could you tell me which font and size you use? It's definitely something about grouping character in groups of 6, I need to revisit the implementation again. If some images don't show then ideally you should open another issue about that. Liebe Grüsse aus der fehrne von Spanien! Benjamin Große

…

On Tue, 14 Apr 2026, 01:09 jemabaris, ***@***.***> wrote: *jemabaris* left a comment (benjajaja/mdfried#92) <#92 (comment)> Lol, looking at my own screenshot I just realized that there actually is inline image rendering but for whatever reason it's only rendering one of about five images or so that should be in the markdown file. I was clearly blind before^^ — Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACLXRZXBYX6DHDS732E6IT4VVXTRAVCNFSM6AAAAACXYBGU2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENBQGE4DKMZVGA> . You are receiving this because you commented.Message ID: ***@***.***>

[jemabaris]

I am using a mono spaced font called MonoLisa which I have patched myself with Nerd Font Glyphs. Font size is 12.0

[benjajaja]

I temporarily installed a version of that font marked as "Nert Font" from some github repo, since it's a paid font, and sadly I can't reproduce the visuals:

I made a PR to add an option --no-text-sizing-protocol which could mitigate your bug. I would really like to fix it though, but I don't know how at this point.

---

Regarding the missing images, html images like <img src="..."> (I assume from your test file), aren't processed at the moment, but you could open an issue for this. Could be tricky, mdfried depends on treesitter-markdown, but surely there is a way to process HTML in a better way than mdfried currently does.

[jemabaris]

Thank you a lot for looking into it and for the detective work you've done (good job on finding the font and even the same markdown file I encountered the issues with :D ! ) You were right about the images, those are parsed HTML style. Regarding the font spacing issue: I believe that the process of patching the font to a nerd font might have something to do with it. I yesterday noticed that ligatures were not working anymore after the patching process. I then also realized that I don't even have to patch the font when using kitty as my terminal as it has automatic fallback for those glyphs if the font doesn't have include them. Long story short, after switching back to the unpatched version I can't reproduce those spacing issues either. Thank you again :)

[benjajaja]

I got the font for testing from here, with nerd fonts included: https://github.com/NoelJacob/Monolisa

I also opened #102 for the HTML-images issue. Closing this now.

[florzanetta]

Hi, I'm having the same issue with FiraCode using Kitty (v0.48), I tried both the nerd font and the non-patched font and I get the same result.

I'd love it if you can consider merging #93 to add the --no-text-sizing-protocol option.

This is the FiraCode version I'm using: https://github.com/tonsky/FiraCode/releases/tag/6.2
And this is the patched version: https://github.com/ryanoasis/nerd-fonts/releases/tag/v3.2.1

Thanks!

[benjajaja]

Yes, it wasn't added because this exact problem got solved for someone. Could you provide which mdfried version you're seeing this in?

Should be easy to add, but it would probably be better as a config option.

[florzanetta]

This version: mdfried 0.22.4

[benjajaja]

Ok thank you, I was hoping that this could be ascribed to using an older version 🥲