Tony Mechelynck <[email protected]> writes:
> On Sun, Nov 8, 2015 at 8:47 PM, Bram Moolenaar <[email protected]> wrote:
>> Instead of removing the documentation, we can add the options.
>> The feature actually is supported. Although it's probably only useful
>> for the GUI.
>
> They give me E846 "Key code not set" which seems to mean that they are
> defined, but not part of the current termcap (I checked builtin_gui,
> xterm and linux, with 'ttybuiltin' on). IIUC the GUI can use undercurl
> without needing those codes? Then they would only be useful in a
> Rolls-Royce of terminals (one can dream…)
It might be nice to turn gvim itself into such a "rolls-royce", and have
all control between the gui layer and other layers be encoded in escape
codes. At the moment, it can't even handle an escape code split across
multiple writes, which aborted my first attempt to make it support
running full-screen terminal apps within it (e.g. :!man).
> which would support
> undercurl by means of escape codes.
Also, how would such an escape code specify the color?
The builtin_gui terminal in the source code _does_ appear to define
them, but incorrectly. I don't know why these definitions don't get
picked up on execution.
{(int)KS_UCE, IF_EB("\033|8C", ESC_STR "|8C")}, /* HL_UNDERCURL */
{(int)KS_UCS, IF_EB("\033|8c", ESC_STR "|8c")}, /* HL_UNDERCURL */
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
