fredizzimo

I don't think that's possible, [Winit](https://docs.rs/winit/latest/winit/index.html) does not provide us that much control. And I'm not sure if the operating system does either. But I'm quite sure that if you...

I tried the Appimage from the artifacts, but unfortunately it does not seem like it fixes the bug, and the environment variable `ARGV0` is still set inside the spawned Neovim...

Perhaps it's not the best place, that code is only called when the config file load fails. https://github.com/neovide/neovide/blob/1db63d93b18cc1eb5ac5b3e67b3ca63505f10800/src/settings/config.rs#L67 But this could also mean that the config file is not working...

I made another fix here and verified that it works: * https://github.com/neovide/neovide/pull/2691 So, closing this one.

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

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.

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...

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...

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...

I'm re-opening this, as I don't think no-tabs is the correct long-term fix.