Re: Patch 8.0.0570

2017-04-21 Fir de Conversatie Christian Ludwig
Hello, > > Travis has GNU coreutils installed. If you check the logs, you'll see that > it finds /usr/local/bin/gmkdir. > Perhaps related: Patch 8.0.0570 deleted src/mkinstalldirs, but this script is still called (without success) in src/installml.sh and src/installman.sh. How is this

Proposed patch for issue 848

2017-02-22 Fir de Conversatie Christian Ludwig
Hello, in the attachment is a proposed patch for Issue 848 for gtk3vim https://github.com/vim/vim/issues/848 [written by Kazunobu Kuriyama (nuko8) and me]. This issue cannot be seen at all window managers [but openbox seems to be a good candidate]. What is changed by the patch? This patch

Re: Feedback for virtcol(), issue 277

2017-01-29 Fir de Conversatie Christian Ludwig
Bram Moolenaar wrote: >> [...] >> Yanking the first 3 visual columns [1,3] of >> a >> a >> the output of >> [...] > > That is correct. For the double-wide character the position of the > right half is given, as documented: > > That is, the last screen position occupied by the character

Re: Feedback for virtcol(), issue 277

2017-01-28 Fir de Conversatie Christian Ludwig
Bram Moolenaar wrote: > > Thanks for explaining. So the '] mark is on the last byte of the > yanked text. I hesitate to change this, since quite a few Vim > functions with byte positions, and the number of bytes between '[ and > '] could be used. > > So we can change virtcol(). I'll make a

Re: Feedback for virtcol(), issue 277

2017-01-27 Fir de Conversatie Christian Ludwig
Bram Moolenaar wrote: >> [...] >> >> I did some tests with virtcol() and compared the results with my >> expectations (which may be plain wrong), see also Issue 277. >> [...] > > You are passing in an invalid position, halfway a character, thus the > returned value is undefined. Thank you for

Feedback for virtcol(), issue 277

2017-01-26 Fir de Conversatie Christian Ludwig
Hello, I apologize if this is the wrong list/place for the following concern: I did some tests with virtcol() and compared the results with my expectations (which may be plain wrong), see also Issue 277. Here is one example of the test-set for the line: a

Re: Very slow scrolling with gtk3

2016-10-05 Fir de Conversatie Christian Ludwig
Hi Taylor, On 30/09/16 14:51, Taylor Venable wrote: > > These all cause the slowness: > > * repeatedly using j / k when the cursor is at the bottom / top of the window > * repeatedly using page down / page up > * repeatedly using mouse wheel down / mouse wheel up > * clicking and dragging the

Re: Asynchronous screen update

2016-04-20 Fir de Conversatie Christian Ludwig
Hello Kazunobu Kuriyama, > Thank you for checking. > >> if I make then the gtk3vim-Window active > > What do you mean by "active"? Raising the window on top of the another > window, or restarting the vim process that had been stopped then? Raising the window on top of the others (=bring to

Re: Asynchronous screen update

2016-04-20 Fir de Conversatie Christian Ludwig
On 19/04/16 11:42, Kazunobu Kuriyama wrote: > 2016-04-19 15:49 GMT+09:00 Bram Moolenaar : > >> >> The GUI cursor blinking restarts the timer every time. That's a >> separate problem though. >> > > Year, that's true. In addition to that, I think the irregularity of the >

Re: confused with patchfiles 1197 and 1203

2016-01-31 Fir de Conversatie Christian Ludwig
Hello Bram Moolenaar, >> 1. confusion (Patchfile 1203) >> >> [...] > My mistake. I'll remove the duplicate. > >> 2. confusion (Patchfile 1197) >> >> Looking at >> http://ftp.vim.org/pub/vim/patches/7.4/7.4.1197 >> in the section for the file src/gui.c (3rd hunk, line

confused with patchfiles 1197 and 1203

2016-01-31 Fir de Conversatie Christian Ludwig
Hello guys, I'm confused. I hope somebody has the time and can help me. 1. confusion (Patchfile 1203) Looking at http://ftp.vim.org/pub/vim/patches/7.4/7.4.1203 in the section for the file src/proto/if_ole.pro (lines 1-5) then the same patch-block (patch-directive) is given twice

issue 393: patch offer

2015-09-08 Fir de Conversatie Christian Ludwig
Hello everybody, are there volunteers to test the patch https://gist.github.com/luchr/42fb32ae0410dfd166cc It tries to fix issue 393 https://github.com/vim/vim/issues/393 The pango_shape_full() function was added to pango in the year 2012 and is available since version 1.32.0 and it is usable