post/neovim-lua-statusline about elianiva.my.id

[luetage]

Great write‐up, thanks for sharing. This was very helpful in getting my own lua statusline going.

[bryant-the-coder]

@elianiva error 404 for neovim-lua-statusline website

[luetage]

https://web.archive.org/web/20210924021734/https://elianiva.my.id/post/neovim-lua-statusline

[elianiva]

@elianiva error 404 for neovim-lua-statusline website

Thanks for pointing out! Should be fixed now.

[bryant-the-coder]

thz... wanna make my own statusline for so long xD

[nathanielevan]

Pretty informative article, great write-up. Coming from someone entirely new to Lua and Neovim as a whole, I have a question that has been lingering on my mind recently: seeing that these functions you defined within M are only used within this Lua file alone, what are the advantages of defining them within a module instead of as "standalone" functions, like so:

function get_git_status()
    -- stuff here
end

I'm seeing a lot of people do it this way (i.e. encapsulating these functions within modules), but I have no idea exactly what purpose it serves.

[elianiva]

I think it's just a personal preference. I prefer to use self to access related values instead of relying on local variables inside this file. It's kinda like using class.

[bryant-the-coder]

hey @elianiva , can u try changing the highlight group when we select the text in ur post?

[mnjm]

Hey, here is the code snippet to replace VimL autocmds with Lua-API

local _au = vim.api.nvim_create_augroup('status_line', { clear = true })
vim.api.nvim_create_autocmd({'WinEnter', 'BufEnter'}, {
    pattern = "*",
    callback = function()
        vim.wo.statusline = statusline.active()
    end,
    group = _au
})
vim.api.nvim_create_autocmd({'WinLeave', 'BufLeave'}, {
    pattern = "*",
    callback = function()
        vim.wo.statusline = statusline.inactive()
    end,
    group = _au
})

[elianiva]

closing since I migrated to giscus