Iordanis Petkakis

This commit now overwrites `lualine`'s statusline when a dashboard is shown. Before this commit it used to show `statusline=%#lualine_transparent#` and after this commit it shows `statusline=%

> you can do vim.o.statusline = " " this worked in my end. That still shows an empty statusline which is visible on the dashboard. Why is this overwriting the...

Yes, I've tried that and it works if I specifically define it `vim.o.statusline = "%#lualine_transparent#"`. I'm asking why it gets overwritten. This did not happen before this commit and it...

I found that lualine only sets the transparent statusline when `vim.go.statusline == ''` (but this is no longer the case after this commit). I'll create an issue over there to...

@luukvbaal Are you referring to me? Because you quoted someone else (English is not native to me and I may be interpreting things wrong based just on the written text)....

As far as I know the docs are automatically generated from the code. And in the code `svim` is a valid wrapper for `vim`, the reason being that in Neovim...

That code is only meant to be used in the Snacks codebase. You should use `vim.fs.normalize` in your configuration. I just don't know if it's an easy fix for the...

Yeah your PR probably won't fix that. But don't close this issue. Maintainer will definitely have a better idea on how to improve the docs.

I believe if you change your configuration into the following ```lua { "folke/snacks.nvim", opts = function(_, opts) opts.lazygit = opts.lazygit or {} opts.lazygit.theme_path = svim.fs.normalize(vim.fn.stdpath("cache") .. "/lazygit-theme1.yml") end, }, ```...

Of course, you are right. I did not insinuate otherwise. I was just playing around to see why it wasn't working and just thought I'd mention the reason here.