Neovide Opening File Opens Same File Twice

[s4Dt0y]

When I open a file like "neovide main.rs", the file opens, but it opens the file twice in two different tabs. How do I open the file only once. Am I missing something here?

[s4Dt0y]

As a side note, one workaround is to use the add the --no-tabs flag.

[fredizzimo]

I can't repeat this here, which platform are you running on?

[carlmueller]

It’s happening to me on MacOS Sonoma.

[s4Dt0y]

I can't repeat this here, which platform are you running on?

I'm on mac sonoma as well...the context for this is trying to set up neovim with unity. I started with trying nvr, but gave up after a couple of days. So I instead tried Neovide which def works better out of the box, but opens up the files twice.

[carlmueller]

The following workaround works for me.

open -a neovide filename

[fredizzimo]

Can someone provide a log file, neovide --log main.rs. I don't have a mac so I can't debug it myself, but maybe I'm able to spot something in the logs.

[carlmueller]

Odd. With neovide --log test.txt the file is not opened twice, but with neovide test.txt it is opened twice. I'm attaching the log file anyway.
neovide_rCURRENT.log

[fredizzimo]

Very strange, maybe the commandline parser interprets the file as both a file to open and neovim arguments. Can you try with neovide main.rs --, forcing the neovim arguments to be empty?

Although, it should be the same on all platforms.

[carlmueller]

neovide test.txt -- still opens the file twice.

[carlmueller]

neovide test.txt --log does open the file twice (while neovide --log test.txt does not). I'm attaching the log file.
neovide_rCURRENT.log

[fredizzimo]

Thanks, so it starts Neovim correctly. "/opt/homebrew/bin/nvim" "--embed" "-p" "test.txt", but additionally there's a TRACE [neovide::channel_utils] UIComand Parallel(FileDrop("test.txt")) event.

So, it seems like macOS is parsing the comandline and invoking the application:openFiles: https://developer.apple.com/documentation/appkit/nsapplicationdelegate/1428742-application handler despite running Neovide directly rather than throuh open and Neovide.app. I can't see anything in the documentation, neither did I find anything doing a quick internet search. So, I don't know how that parsing is done.

[fredizzimo]

Here's the stupid design Apple has decided to implement
https://lists.apple.com/archives/cocoa-dev/2009/May/msg00480.html,

TLDR; there's no way to disable the built in parsing of the arguments, so we need to ignore the openfile requests for them, or maybe always only use openfile, and ignore the initial arguments.

The problem is that I can't find any official documentation of this, and nothing about what the scheme it uses, if everything that looks like a file is passed to openFile, or if the file actually has to exist for example. And in both cases we need to be able to filter the list of arguments.

I guess that's something for the one actually fixing the bug to find out...

We might also want to delay the initial file list parsing, see

• macOS: initial opening via open -a "Neovide" does not set arglist #2629