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

perf: socket server #39

Merged
merged 33 commits into from
Aug 11, 2023
Merged

perf: socket server #39

merged 33 commits into from
Aug 11, 2023

Conversation

linrongbin16
Copy link
Owner

TODO: the manual testing is failed

I have no idea why TCP socket on 127.0.0.1:0 failed, the log shows serverstart is success, but sockconnect failed.

Maybe I should try pipe mode?

@linrongbin16 linrongbin16 changed the title feat: socket server perf: socket server Aug 9, 2023
@linrongbin16
Copy link
Owner Author

linrongbin16 commented Aug 11, 2023

Now I use the serverstart and sockconnect API to connect to the server inside nvim editor, it works, but it will break the running fzf terminal, so the UI looks like it blink.

That's really ugly, but for now it's the only solution I got.


Oh! I found I made a mistake, in previous debugging I use execute(...) in fzf options, now I revert it back to execute-silent(...) and everything is good now!

Also see wiki: https://github.com/linrongbin16/fzfx.nvim/wiki/How%3F#setup-socket-server-to-do-calculation-for-lua-scripts-executing-from-fzf

TODO: test on Windows.

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

Successfully merging this pull request may close these issues.

1 participant