-
Notifications
You must be signed in to change notification settings - Fork 166
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(win)!: support additional border styles (#1668)
Refactor win class code: - Support both neovim and fzf border styles for `winopts.border|winopts.preview.border`, styles inlcude: ``` # `nvim_open_win` styles none single double rounded solid shadow # fzf-lua styles (some are aliases) empty bold block solidblock thicc thiccc thicccc # fzf borders border noborder border-none border-rounded border-sharp border-bold border-double border-block border-thinblock border-horizontal border-top border-bottom ``` - Improve `treesitter-context` attach - Refactor (normalize) layout generation code - Refactor scrollbar code - Refactor preview border: remove dedicated border window and use `nvim_open_win` title options instead (neovim >= 0.9) - Fix scroll position caching with entries that have no line|col - Fix fullscreen with `winopts.relative=cursor` - Added an option for custom `winopts.split` function, this enables the use to create their own window for fzf-lua Other changes: - Require Neovim 0.7, remove backward compat code for 0.5|0.6 - Default profile set to `default-title` on neovim >= 0.9 - Renamed profile `borderless_full` -> `borderless-full` - Modify profiles `borderless|borderless-full` to use the new border options - New profile: `border-fused`, fuse fzf and preview window together with minimum spacing, will look similar to fzf's native layout where the preivewer is "contained" inside fzf
- Loading branch information
Showing
19 changed files
with
544 additions
and
619 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.