Open Sduby22 opened 2 years ago
I found that you have forked my repo and combined alohaia/fcitx.nvim and h-hg/fcitx.nvim.
In the early verison, I also used io.popen
or os.execute
to call fcitx-remote. However, the neovim will display the log message or the error message when using fcitx-remote in OSX. And it has been found in issue 2.
An simple way to reproduce it is that you replace the fcitx-remote -c
/ fcitx-remote -o
with a program which writes log message. For exmaple,
#include <iostream>
using namespace std;
int main() {
cout << "std out\n";
cerr << "error out\n";
clog << "log out\n";
return 0;
}
I don't know why vim.fn.system
doesn't display.
alohaia/fcitx.nvim
: no sensible lag when changing modes.h-hg/fcitx.nvim
: perceptible lag (~100ms) on mode switch.runs on Manjaro Linux with
fcitx5-remote