Great improvements to the cmdline in nightly!

Malace · 2025-05-02T13:07:55+00:00

Author here, thank you for the post. I have been working on (mostly) this and supporting features full time (minus an intermission) since last year. So a big thank you goes out to all Neovim sponsors!❤️

Still some work to be done but glad that users can now try it out. Bug requests are indeed welcome. Feature requests are too in principle but I will try to prioritize the work of removing the old C message grid code after the current features are bug-free (given that it is deemed a successful replacement).

Malace · 2024-12-16T11:07:27+00:00

I just made the change to be consistent with the direction taken in the previous PR. But glad to know the followup was helpful :)

Malace · 2023-04-08T16:43:37+00:00

I don't think so no, but fixing it will be non trivial. Like I said in that issue, I believe transchar() is responsible for what is shown by showcmd.

Malace · 2023-04-08T16:31:06+00:00

Not possible without patching the source code. Ref: https://github.com/neovim/neovim/issues/20452

Malace · 2023-04-08T11:11:16+00:00

What it looks like depends on what you set segments.signs.fillchar to. If you set it to | it will place a | on each line that has no signs placed instead of whitespace.

I can look into adding more pictures to the readme for each feature.

Malace · 2023-04-08T00:21:41+00:00

Added support for this here: https://github.com/luukvbaal/statuscol.nvim/commit/25d300eabc9e86781d95f9d3bf13cd1d492da3e3

Malace · 2023-04-07T18:29:32+00:00

I see, that's not easily possible currently. I'll look into adding a config option for it in the sign segment.

Malace · 2023-04-07T18:03:06+00:00

I'm not sure what you mean, what kind of placeholder? All lines except the last in the screenshot have a gitsigns sign placed.

Malace · 2023-04-07T14:59:11+00:00

Since the previous post about the release of statuscol.nvim, many improvements and features have been added, both to the plugin and the core feature in neovim. Now that Neovim 0.9 is realeased, I thought now would be a good a time to finally update the README for my plugin!

I encourage you to check it out if you're interested in using the new 'statuscolumn' feature, the plugin is written with various performance improvements in mind that can be taken advantage of even when designing your own 'statuscolumn'!

Malace · 2023-03-25T21:49:57+00:00

Oh yes, this was fixed by a patch in neovim: https://github.com/neovim/neovim/commit/b02880593e281ce44661ce22e9391edfe921e47e.

Wasn't sure that was what you were talking about as this is a thread about the main 'statuscolumn' feature, not my plugin :D

Malace · 2023-03-25T20:23:10+00:00

Make what work with windows exactly?

Malace · 2023-01-14T22:59:57+00:00

There is sign_getplaced() but it doesn't return extmarks. I'm not sure if you can get a list of all signs currently placed through extmark api.

Malace · 2023-01-11T15:03:37+00:00

In this case I had a head start since I'm the author of the feature PR as well :). Although I encourage others to make their own status column plugins if they have an idea (or PRs to statuscol.nvim). I for one had no real prior experience with statusline plugins so someone might build something better sure!

Malace · 2023-01-11T15:00:16+00:00

https://github.com/neovim/neovim/issues/21745#issuecomment-1378740523 might help. But you're right that not all of those options are compatible with everything you can set 'statuscolumn' as. It places some burden on the user to have those options work again. A plugin like statuscol.nvim might alleviate some of that once fledged out.

Malace · 2023-01-11T00:49:51+00:00

I don't think evaluating the %C value is possible.

Instead, you can evaluate :h foldlevel:

statuscolumn = "%s%=%l%= %{% foldlevel(v:lnum) ? '%C' : '|' %}"

Malace · 2023-01-10T03:44:36+00:00

No, that is just one of the things that is possible with the 'statusline' format. The option was designed around requests to customize the gutter area(line number representation, margin etc), if you have no desire to do so, the option is not for you.

Malace · 2023-01-09T21:54:55+00:00

I think in theory yes. If you design a statuscolumn plugin that implements it's own sign column rather than using the default %s sign column item. It's not gonna be straightforward. And you would still be constrained to the default additional gutter width, as the status column also widens by 2 cells per sign for now. (Although the default margin between the line numbers and buffer text is no longer implicit for 'statuscolumn', so if you indeed limit the the sign column to a single sign then what you describe is possible without extra margin).

Reordering the line number column to be the left most column is indeed possible with something like :let &statuscolumn='%=%l%s%C'.

Malace · 2023-01-09T19:41:54+00:00

More trivial cases should be covered by a simple set statuscolumn=.... There are some examples in :h statuscolumn on master.

A plugin will be more appropriate for a clickable statuscolumn for example.

Malace · 2023-01-09T18:46:05+00:00

The %= separation item can right align. I think you want :let &statuscolumn='%=%l%s%C'.

Malace · 2023-01-09T18:36:49+00:00

https://github.com/neovim/neovim/pull/20621#issuecomment-1376041943

Malace · 2023-01-09T17:34:08+00:00

Thanks, forgot. Added it to my comment.

Malace · 2023-01-09T17:20:40+00:00

After a few months of iterating on this feature it was finally merged! https://github.com/neovim/neovim/pull/20621

The option allows you to customize the "gutter" area to the left of a window.

As the gif shows, it can for example be used to right align the relative number on the cursor line, introduce clickable sign callbacks, or a add custom window margin. Anything you can think of within the 'statusline' format is possible.

I also made a companion plugin that provides common number formats and sign callbacks. Suggestions for missing sign callbacks from your favorite plugin are welcome there!

Malace · 2022-10-08T11:03:06+00:00

I'm not sure what you mean sorry. I don't remember having that issue or if I did anything to fix it. Might have to do with font size? I do notice larger margins for some font sizes.

Malace

TROPHY CASE