Edit icon of vi_mode without changing anything else from feline

[marcelarie]

Is it possible? I want to specify parameters for single components, for example changing the icon of the vi_mode component.

This is my config:

return {
	"freddiehaddad/feline.nvim",
	config = function(_, _opts)
		require("feline").setup()

		local lighthaus_theme = {
			fg = "#DCD7BA",
			bg = "#1F1F28",
			black = "#16161D",
			skyblue = "#16161D",
			cyan = "#6A9589",
			green = "#76946A",
			-- oceanblue = "#658594",
			oceanblue = "#1F1F28",
			magenta = "#D27E99",
			orange = "#FFA066",
			red = "#E82424",
			violet = "#957FB8",
			white = "#DCD7BA",
			yellow = "#FF9E3B",
		}

		require("feline").use_theme(lighthaus_theme)

		-- require("feline").winbar.setup()
	end,
}

[freddiehaddad]

To answer your question. Yes, this can be done. There's an example here of how to create and customize components as well as lots of examples in the documentation.

Here's a custom example: https://github.com/freddiehaddad/nvim/blob/main/lua/plugins/feline.lua plus link to the specific vi-mode section: https://github.com/freddiehaddad/nvim/blob/209754268058239818e4c8cd49e4342d64ce3abe/lua/plugins/feline.lua#L326-L339

What you're wanting to do it sounds like is modify a component to change it's behavior. The documentation shows how to do that. I think in combination with the links I shared, you should be able to accomplish what you want. I can elaborate more if needed. Please let me know.

[marcelarie]

By the way, the link that you shared here is broken. It should link to this discussion, 81 and not 80.

[freddiehaddad]

Yes, that is possible.

For the vi_mode, since you want to change the behavior outside of the built-in configurable options, you need to re-create the module with your custom changes. For the built-in ones that you want to leave as-is, you just need to reference the provider name.

You will need to explicitly name the components you want in the active list (which is what I think you're wanting to avoid). While not convenient, it would be harder to try and figure out what the user wants and doesn't want otherwise. So once you deviate from the default, you have to provide everything. But it's just a matter of providing the component name. No extra coding.

So for example, if you want custom vi_mode and built-in filename.

You would do something like:

local c = {
    custom_vi_mode = { ... your custom behavior ... },
    file_name = { provider = { name = 'file_info' } },
}
local active = {
    c.custom_vi_mode,
    c.file_name,
}

[marcelarie]

Gotcha, that is what I thought. I think it would be awesome to reference the default active and inactive components by a require and do something like this:

local function config(_, opts)
  local active = require('feline.defaults.active');

  active.providers.vi_mode = {
    icon = "∆",  -- No need to re-declare anything else, it will use the defaults.
  }

  opts.components = { active = active } -- No need to declare the inactive providers, it will use the defualts
  feline.setup(opts)
end

I think this will make the plugin much more user-friendly. I know the special part about feline is the modularity but personally I think this is better.

[freddiehaddad]

That's great feedback and something I would like to implement. When I have a few days to sit and think it through I will work on it. I think it can be accomplished without breaking people's configs. That's always the tricky part.

[marcelarie]

I will keep an eye on the following updates then, thanks!

[freddiehaddad]

By the way, the link that you shared here is broken. It should link to this discussion, 81 and not 80.

Yeah, sorry about that. Because the issue is closed, I can't update the link. :(