Christian wrote:
> I noticed two inconsistencies.
>
> There is (only one) tag guioptions_a. In addition each flag has the
> 'go-' tag entry, so I suggest to remove the guioptions_a flag.
There is one place where it's used, we can change that to go-a.
> win_getid() says this:
>
> ,
> |
Bram,
I noticed two inconsistencies.
There is (only one) tag guioptions_a. In addition each flag has the
'go-' tag entry, so I suggest to remove the guioptions_a flag.
win_getid() says this:
,
| When {win} is missing use the current window.
| With {win} this is the window number. The top
On Wed, Oct 24, 2018 at 1:57 PM John Little wrote:
>
> I noticed a problem today when editing a paragraph that was wrapped to
> several lines on screen. To reproduce, use a file with a line with normal
> prose text that wraps to several screen lines, say x.txt, then
>
> vim -u NONE -c "set
I noticed a problem today when editing a paragraph that was wrapped to several
lines on screen. To reproduce, use a file with a line with normal prose text
that wraps to several screen lines, say x.txt, then
vim -u NONE -c "set linebreak showbreak=>" x.txt
Move to the end of the long
