Skip to content

Conversation

@Vagahbond
Copy link
Contributor

Add an option to open codewindow on NVF launch

Pretty straightforward

Sanity Checking

  • I have updated the changelog as per my changes
  • I have tested, and self-reviewed my code
  • My changes fit guidelines found in hacking nvf
  • Style and consistency
    • I ran Alejandra to format my code (nix fmt)
    • My code conforms to the editorconfig configuration of the project
    • My changes are consistent with the rest of the codebase
  • If new changes are particularly complex:
    • My code includes comments in particularly complex areas
    • I have added a section in the manual
    • (For breaking changes) I have included a migration guide
  • Package(s) built:
    • .#nix (default package)
    • .#maximal
    • .#docs-html (manual, must build)
    • .#docs-linkcheck (optional, please build if adding links)
  • Tested on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin

Add a 👍 reaction to pull requests you find important.

@github-actions
Copy link

github-actions bot commented Dec 3, 2025

🚀 Live preview deployed from 26c4a7e

View it here:

Debug Information

Triggered by: Vagahbond

HEAD at: codewindow-open-by-default

Reruns: 1658

Copy link
Owner

@NotAShelf NotAShelf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather if this plugin was converted to setupOpts.

@Vagahbond
Copy link
Contributor Author

Ill see what I can do with HR

@NotAShelf
Copy link
Owner

Should be trivial, barely a breaking change.

If you don't do it now you are FIRED

codewindow: allow opening on setup
@Vagahbond Vagahbond force-pushed the codewindow-open-by-default branch from 082e0cd to 232e4a0 Compare December 3, 2025 21:24
@Vagahbond
Copy link
Contributor Author

Please don't fire me I'll make you coffee ☕

@Vagahbond Vagahbond requested a review from NotAShelf December 4, 2025 05:02
@NotAShelf
Copy link
Owner

Ok you're not fired

NotAShelf
NotAShelf previously approved these changes Dec 4, 2025
@Soliprem
Copy link
Collaborator

Soliprem commented Dec 7, 2025

CI failure is unrelated

github-actions bot pushed a commit that referenced this pull request Dec 7, 2025
Copy link
Collaborator

@Soliprem Soliprem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing the release notes entry (something along the lines of "moved codewindow to setupOpts" should be fine)

@Vagahbond
Copy link
Contributor Author

Will do after breakfast

codewindow: allow opening on setup
in {
options.vim.minimap.codewindow = {
enable = mkEnableOption "codewindow plugin for minimap view";
openByDefault = mkEnableOption "codewindow plugin opening automatically";
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no-op?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oopsie failed conflict resolution

Comment on lines 20 to 29
description = "Open automatically";
type = bool;
default = true;
};

exclude_filetypes = mkOption {
description = "Excluded files types";
type = listOf str;
default = ["NvimTree" "orgagenda" "Alpha"];
};
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can leave the mkPluginSetupOption args empty:

mkPluginSetupOption "codewindow" {}

and since it's always freeform, you'll be able to pass any option that you want. See the setupOpts section in the manual. I think this PR would be better off only converting to setupOpts instead of introducing new options, which we're trying to move away from.

Comment on lines 36 to 38
codewindow.setup(
${lib.nvim.lua.toLuaObject cfg.setupOpts}
)
Copy link
Owner

@NotAShelf NotAShelf Dec 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
codewindow.setup(
${lib.nvim.lua.toLuaObject cfg.setupOpts}
)
codewindow.setup(${cfg.setupOpts})

No reason not to inline this. You can also move the lib.nvim.lua.toLuaObject part to an inherit at the top, but not a hard-requirement.

Comment on lines +523 to +525
[vagahbond](https://github.com/vagahbond):

- moved [codewindow](https://github.com/gorbit99/codewindow.nvim) to setupOpts
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please match rest of the documentation, and format the file with deno fmt.

@Vagahbond Vagahbond requested a review from NotAShelf December 7, 2025 22:19
Soliprem
Soliprem previously approved these changes Dec 8, 2025
@Vagahbond
Copy link
Contributor Author

Don't merge it's actually broken
Ill fix asap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants