Mouinul Hossain

@Saghen, Shouldn't a simple eval function be enough for this? ```lua ---@param val table ---@param ignore string[] Ignore these keys(e.g. some function that needs to be run on something instead...

> that would lose type checking Can't we simply use 2 type definition, 1 exposed to the user and 1 used internally. ```lua ---@class config.window ---@param X string | fun():...

Also, I think it would be simpler to assume everything inside `window` can be a function, instead of handling specific options differently.

Sure. I would suggest not to do any direct function call for getting the value. > `nvim-cmp` does this and there were plenty of time when I got soft locked...

> but you can find them scattered in the codebase It appears that I didn't check throughly enough. Oh well, I guess you can just ignore my previous comment.

Possible solutions, - [ ] Patching nerd fonts using `fontforge`(apply 2D transformation & scale). > This would require knowing how much the text is getting offset. I have also noticed...

> Did you try to install a font which support those characters? Yes and that's not even related to the issue(I mentioned it because it's easier to see in nerd...

Just to clarify, this is an issue with the ~~font~~**text renderer** itself.

> Also just a heads up, the parser behaves weirdly with the following text: Can you elaborate? Does it not look something like this?  >[!NOTE] > Tree-sitter won't...

> Maybe we can omit that injection here and leave it for the plugin to ; extend with? So, do I add it to the parser's README that it exists?...