Did you check the docs and existing issues?

• I am using latest nougat.nvim
• I have read all the nougat.nvim docs
• I have searched the existing issues of nougat.nvim

Problem

https://github.com/MunifTanjim/nougat.nvim/blob/main/lua/nougat/nut/buf/filetype.lua, the filetype component don't have 'format' function, which cannot use devicons to show the colored file type icons.

lualine have filetype icon:

Solution

add 'format' function to allow user do customization.

Alternatives

No response

Additional Context

No response

Did you check the docs and existing issues?

• I am using latest nougat.nvim
• I have read all the nougat.nvim docs
• I have searched the existing issues of nougat.nvim

Problem

I want to display a clock, but it is not updating.

nougat.nvim config

-- datetime {{{
local datetime = (function()
  local item = Item {
    sep_left = sep.left_half_circle_solid(true),
    content = {
      Item {
        hl = { bg = color.green, fg = color.bg },
        content = vim.fn.strftime('%H:%M'), -- FIXME: Not refreshing
      },
    },
    sep_right = sep.right_half_circle_solid(true),
  }

  return item
end)()
-- }}}

-- statusline {{{
local stl = Bar('statusline')
stl:add_item(datetime)
bar_util.set_statusline(stl)
-- }}}

Solution

Clock is refreshed.

Alternatives

No response

Additional Context

No response

Did you check the docs and existing issues?

• I am using latest nougat.nvim
• I have read all the nougat.nvim docs
• I have searched the existing issues of nougat.nvim

Problem

This is not a bug, much more relate to system design.

But I think it's worth to discuss, when people use (for example) color.yellow config/API, I believe this API is going to try to retrieve color from a syntax highlighting group (for example 'Visual'), if failed it's going to use yellow color as fallback.

But people will not know what highlighting it's going to use.

We could either document it explicitly, or change the API to color.yellow('Visual') to be more explicit, and even people can customize the highlighting group name by themselves.

Solution

Already in Problem section.

Alternatives

No response

Additional Context

No response

It would be also very nice if we could see LSP information on the statusline.

What information would be helpful to debug?

Did you check the docs and existing issues?

• I am using latest nougat.nvim
• I have read all the nougat.nvim docs
• I have searched the existing issues of nougat.nvim

Problem

I'm using vim-gitbranch as git branch data source, and vim-gitgutter as git diff/status data source.

I know most people are using gitsigns, but it has some small bugs on Windows, gitgutter has much better cross-platform compatibilities.

For now I'm configure it with:

local function git_branch()
    if vim.g.loaded_gitbranch == nil or vim.g.loaded_gitbranch <= 0 then
        return ""
    end
    local name = vim.fn["gitbranch#name"]()
    return name or ""
end

local function git_diff()
    if vim.g.loaded_gitgutter == nil or vim.g.loaded_gitgutter <= 0 then
        return ""
    end
    local changes = vim.fn["GitGutterGetHunkSummary"]()
    if changes == nil or #changes ~= 3 then
        return ""
    end
    local symbols = { "+", "~", "-" }
    local builder = {}
    for i, c in ipairs(changes) do
        if type(c) == "number" and c > 0 then
            table.insert(builder, string.format("%s%d", symbols[i], c))
        end
    end
    return table.concat(builder, " ")
end

-- git branch and status
stl:add_item(Item({
    hl = { bg = color.magenta, fg = color.bg },
    sep_right = sep.right_upper_triangle_solid(true),
    prefix = "  ",
    suffix = " ",
    type = "lua_expr",
    content = function(ctx)
        local branch = git_branch()
        if string.len(branch) == 0 then
            return ""
        end
        local changes = git_diff()
        if string.len(changes) == 0 then
            return branch
        else
            return branch .. " " .. changes
        end
    end,
}))

It is working, looks like:

But I want to enable the green, yellow, red colors for the added, changed and removed lines count number.

How should I do it?

I am using the slanty.lua template, the git status sample is:

-- -- git changes
stl:add_item(nut.git.status.create({
    hl = { fg = color.bg },
    content = {
        nut.git.status.count("added", {
            hl = { bg = color.green },
            prefix = "+",
            sep_right = sep.right_upper_triangle_solid(true),
        }),
        nut.git.status.count("changed", {
            hl = { bg = color.yellow },
            prefix = "~",
            sep_right = sep.right_upper_triangle_solid(true),
        }),
        nut.git.status.count("removed", {
            hl = { bg = color.red },
            prefix = "-",
            sep_right = sep.right_upper_triangle_solid(true),
        }),
    },
}))

It seems the content in nut.git.status.count is not overwrite-able, correct?

Solution

Use self-defined data source for git status.

Alternatives

No response

Additional Context

No response

Did you check the docs and existing issues?

• I am using latest nougat.nvim
• I have read all the nougat.nvim docs
• I have searched the existing issues of nougat.nvim

Problem

get_content of LSP config is currently hardcoded to a set function

Solution

Allow for a configurable opts to be passed to allow overriding the default implementation

Alternatives

An alternative would be created the Item then merging it with another table that has my custom function

local item = nut.lsp({
  config = {},
  prefix = "  ",
  hl = { fg = color.green },
  sep_right = sep.right_chevron_solid(true),
  on_click = function()
    vim.cmd("LspInfo")
  end,
})

stl:add_item(Utils.merge(item, { content = custom_content_fn }))

Additional Context

No response

i saw this snippet in the examples:

stl:add_item(Item({
  hl = {fg = color.bg, bg = color.fg0},
  prefix = ' ',
  suffix = ' ',
  content = core.group({core.code('l'), ':', core.code('c')})
}))

is it somehow possible to get the number of lines a file has too with core.code?

i could not find the documentation for it.

Instead of hardcode color palettes, could we consider extract the existing palettes from the current using colorscheme? that way the statusline style would be very naturally blended in with the rest of themes.

• Mode - #6
• Ruler - #8
• Spacer - #7
• File Encoding - #14
• File Format - #13
• File Name - #15
• File Type - #12
• Diagnostic Count - #9
• Word Count - #10
• Git Branch - #16
• Tab List - #23 #30
• Win List - #83
• Buf List
  • Tab Scoped - #84
  • Win Scoped -
• File Status - #31

hey hey,

awesome plugin, thx for writing it!

is it possible to change the colors for the different modes like normal, visual, insert?
i looked at the 3 examples and wasn't able to find it?

the same goes for the diagnostic_count?
can i somewhere change these too, like i'll do it for the git counts?

thx again for the plugin!

E5108: Error executing lua Error executing lua: ...cal/share/nvim/lazy/nougat.nvim/lua/nougat/item/init.lua:117: attempt to index local 'cache' (a function value)
stack traceback:
	...cal/share/nvim/lazy/nougat.nvim/lua/nougat/item/init.lua:117: in function 'item'
	/Users/dsully/.config/nvim/lua/plugins/nougat.lua:156: in function 'content'
	...y/.local/share/nvim/lazy/nougat.nvim/lua/nougat/util.lua:388: in function 'prepare_parts'
	...ocal/share/nvim/lazy/nougat.nvim/lua/nougat/bar/init.lua:118: in function 'generate'
	...ocal/share/nvim/lazy/nougat.nvim/lua/nougat/bar/util.lua:19: in function <...ocal/share/nvim/lazy/nougat.nvim/lua/nougat/bar/util.lua:17>
	[C]: at 0x0100ec0e38
stack traceback:
	[C]: at 0x0100ec0e38

This started happening with change dba049f or more likely 45cc6e6 which started using the cache.