Remove title from signature or info window

[Gael-Lopes-Da-Silva]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.completion

Question

Is it possible to remove the title of those window ? With mini.notify, we can just make window.config.title an empty string.

Also, since handlers changed in neovim 0.11. How can I put a title to the hover window ?

[echasnovski]

Is it possible to remove the title of those window ?

Not right now, no. Can I ask what is the motivation here? Personal dislike of titles in floating window or is there some usability issues?

The problem with this is that 'mini.completion' only supports selected fields for window config. Others are computed based on the several factors for every execution and exporting them would only bring troubles. It is possible, of course, to export configurable title, but that would also somewhat imply exporting title_pos (and maybe even footer + footer_pos) which goes against the overall design of having as small config as possible.

Also, since handlers changed in neovim 0.11. How can I put a title to the hover window ?

I am not sure how this relates to 'mini.completion', as it doesn't implement any hover. Can you elaborate, please?

[Gael-Lopes-Da-Silva]

I'll take a moment to think whether I'd want to open the box of adding extra title/title_pos/etc. or whether this kind of solution would be enough (maybe behind custom event for each window?).

I don't really understand the complexity added by those options. By that I mean, does the fact that mini.notify or other mini.nvim plugins, have a window.config add complexity ?

(maybe behind custom event for each window?)

You mean, the above solution with an event like MiniFilesOpen (or something like that). Since it give the user the ability to configure any window that mini.nvim plugins use, this can be a pretty good solution without adding complexity but at the user friendlyness cost.

[echasnovski]

I'll take a moment to think whether I'd want to open the box of adding extra title/title_pos/etc. or whether this kind of solution would be enough (maybe behind custom event for each window?).

I don't really understand the complexity added by those options. By that I mean, does the fact that mini.notify or other mini.nvim plugins, have a window.config add complexity ?

This was already answered in my first comment:

The problem with this is that 'mini.completion' only supports selected fields for window config. Others are computed based on the several factors for every execution and exporting them would only bring troubles. It is possible, of course, to export configurable title, but that would also somewhat imply exporting title_pos (and maybe even footer + footer_pos) which goes against the overall design of having as small config as possible.

[Gael-Lopes-Da-Silva]

Sorry to reopen this, but the autocommand solution does not work anymore.
E.g the first info window shown when completion menu is open does not have a title as per the autocommand configuration bellow, but navigating throught the completions and showing other info windows seams to reset the config.

vim.api.nvim_create_autocmd('BufWinEnter', {
    desc = "Removes title from minicompletion windows",
    group = group,
    callback = function(args)
        local completion_type = vim.api.nvim_buf_get_name(args.buf):match('^minicompletion://%d+/(.*)$')
        if completion_type == nil then return end

        local win_id = vim.fn.win_findbuf(args.buf)[1]
        local config = vim.api.nvim_win_get_config(win_id)
        config.title = ""
        vim.api.nvim_win_set_config(win_id, config)
    end,
})

[echasnovski]

Yes, indeed, there was an update that reduces flicker in info window by not constantly close-opening it when navigating up/down. This means that BufWinEnter is executed only once first time and later gets overridden by default config.

I'll take a look into preserving "decorative" window config fields (like border and title).

[echasnovski]

This should now be resolved on latest main. With tests, so that it won't be accidentally reverted again in the future :) So I am going to close this.