search

yatli / fvim

Cross platform Neovim front-end UI, built with F# + Avalonia
MIT License
1.34k stars 30 forks source link

FVim crashes while using trydaemon in Windows #138

Closed aravind2612krishna closed 4 years ago

aravind2612krishna commented 4 years ago

image Above is the stack trace popup Maybe other info : I called FVimDetach earlier

aravind2612krishna commented 4 years ago

Now I'm not sure if it is because I used --trydaemon, with d small instead of --tryDaemon, which doesn't crash, but doesn't produce anything either. What I guess I'm asking for from this great GUI client is better error messages.

yatli commented 4 years ago

yes the --tryDaemon arg is case sensitive. I'll think about the error handling part. Originally I hope the stacktrace will give back something useful but it looks like everyone is getting a "task was cancelled" nonsense message.

Before you start a client, did you use fvim --daemon to start the daemon?

aravind2612krishna commented 4 years ago

fvim --daemon fvim --tryDaemon

opens no fvim for me, sadly. fvim built from source Release at commit 7a2270c150c407a06

yatli commented 4 years ago

hmmm.. fvim --tryDaemon does the following things:

  1. Check if a fvim daemon exists, and try to connect
  2. If there's no daemon, start an embedded instance.

None of the above happens?

aravind2612krishna commented 4 years ago

Actually both seem to be launching an FVim now, I fail to see how to use it. When we use the daemon, is it to purely reduce startup time? or does it connect to the same underlying neovim instance, and remembers buffers, windows etc, (like session opts) and allow for shared editing?

yatli commented 4 years ago

or does it connect to the same underlying neovim instance, and remembers buffers, windows etc, (like session opts) and allow for shared editing?

Yes. You can use :FVimDetach and connect back with another client. Or even connect two clients at the same time :)

aravind2612krishna commented 4 years ago

Thanks for the great app. Feel free to close this issue, as I have your attention, I'd like to ask one more question if you don't mind. Can I connect to a remote named pipe as below fvim --daemon --daemonPipe fvimserver on Remote: fvim --connect \\<UNC or IP>\pipe\fvimserver

yatli commented 4 years ago

I haven't tested this but had success with a tcp socket. Should be supported. Use with caution. May have security issues.