Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

neovim-qt as a proper MacOS application #1072

Open
bboles opened this issue Jun 28, 2023 · 1 comment
Open

neovim-qt as a proper MacOS application #1072

bboles opened this issue Jun 28, 2023 · 1 comment

Comments

@bboles
Copy link

bboles commented Jun 28, 2023

Thanks for for neovim-qt! It has been critical for me in moving to Neovim!

I know that there has been some effort to get neovim-qt setup as a proper MacOS application:
#850
#848

I did not find any additional activity regarding this effort. Can you tell me the status of setting up neovim-qt so that it behaves like a MacOS app, mainly grouping together multiple windows of neovim-qt in the dock?

@equalsraf
Copy link
Owner

Currently no one is working on this that I know of.

From 848 the changes were merged and a function was added to spawn a window e.g. :call GuiNewWindow({}). That much seems to work here, but this is not a feature I have used much, so I can't offer much more information.

In a nutshell

  1. if you want a new window try :call GuiNewWindow({}) this will be a completely separate neovim with NO shared buffers, tabs, etc. The help docs describes the arguments, but in most cases I think calling it with an empty dict is what you want
  2. We do not currently support a way to start a second neovim-qt window from outside neovim

Concerning point 2. last time we discussed it we did not have a solution to choose which window a file should open on. neovim-qt does support open -a nvim-qt but I am unsure how it currently behaves (i think it opens the file in the first window).

I would also note that things have changed in the neovim side since this was implemented. nvim now has --server and --remote, --remote-send, etc. So maybe there are better solutions using those options.

You can probably hack something such as nvim --server /path/to/nvim.socket --remote-send ':call GuiNewWindow({})<CR>' if you already know the correct argument for the --server option.

Note: looks like we lack a GuiNewWindow command. Should be easy to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants