The fussy package now comes with helper functions to strip down an input
string, removing all extra "tofu" characters added by Consult. This is
also faster than the old hand-rolled solution I had come up with
previously.
Hence I've switch to simpler variant that uses a custom scoring function
that calls `flx-rs-score`, with `str` having been sanitized with the
function assigned to `fussy-remove-bar-char-fn`, which by default is
`fussy-without-tofu-char`.
I've also submitted a PR to fussy that will cleanup the input string
when using flx-rs:
https://github.com/jojojames/fussy/pull/36
Minor changes were needed due to recent lsp-mode changes. My custom the
bufls and golangci-lint clients are now part of lsp-mode.
Also, within Ruby buffers I need to disable the vue-semantic-server
client, as that seems to take priority over Ruby clients in Rails
projects that use Vue.
Previously the active tab was the same background color as normal
buffers, while the rest of the tab-bar had an alternative background
color.
I feel that it visually fits better when these are swapped, so tab-bar
overall has the same background color as normal buffers, and the active
tab has an alternative background color.
Add a new vendored custom package called tab-bar-notch, which resizes
the tab-bar height to match that of the physical camera notch on modern
MacBook Pro models.
yank-indent is more focused on specifically indenting after yank, and
the PR to enhance snap-indent with some similar features has been open
for some time now with no movement.
Solargraph implements the rename feature, but it is horribly broken and
actively destructive causing random changes all over the whole project
whenever it is used.
For a couple of years now, there's been a bug on macOS with the
non-native fullscreen implementation. When enabling fullscreen, any
child-frames created by packages like lsp-ui, company-box, posframe,
etc. all re-appear on top of the fullscreened frame, and stay there
until you re-trigger whatever package/command that created the
childframe originally.
This works around this issue by simply closing all child frames when
toggling non-native fullscreen.