Open rti opened 7 years ago
Before we start the socket feature, we should make sure the key processing works right #247. At the time the key events are transalted into internal 1 or 3 Byte char sequences that are given to the current active mode. But by the translation into multiple chars that are given one by one to the mode we can't get the original key from them. This bug also exist in webkit1 vimb where the formfiller did not work properly in case the form data contained utf-8 chars which where translated into 3 Byte char sequences.
This issue has been automatically marked as stale because it has not had activity within the last 60 days. It will be closed after 7 days if no further activity occurs. Thank you for your contributions.
@fanglingsu very like to see this feature.
me too!
Independent from the lagging utf8 support in the current key mapping logic we could add socket support by restricting this to run only ex commands. This limits the use case but the normal mode commands could still be triggered by :normal ...
.
Socket support --socket,-s and --dump,-d option to print the actual used socket path to stdout
Implemented in vimb2 already. The code [1] and [2] can be used as a reference.
[1] https://github.com/fanglingsu/vimb/blob/2.12/src/main.c#L1915-L1926 [2] https://github.com/fanglingsu/vimb/blob/2.12/src/io.c