Bram Moolenaar

Who has tried out this patch? Is it useful and does it work properly?

> > Instead of numbers, wouldn't it be better to use strings for the > > splitscroll option? > > Numbers seems to be the convention for similar options. See...

> > Those options were added long ago. These days we don't care so much > > for the extra memory use, and care more for easy of use (since...

> @luukvbaal commented on this pull request. > > > @@ -1327,6 +1333,11 @@ win_split_ins( > msg_col = 0; // put position back at start of line > } >...

> The strategy is to keep all lines on the same actual terminal line, > updating the cursor to a valid position rather then scrolling when > necessary. To do...

> Copying from my recent dup, #4275: > > Right now, the list of paths to search for the user's `vimrc` on Linux is: > > ``` > ~/.vimrc >...

I'm afraid that the more I read about the XDG so-called standard the more questions pop up. Hardly anything is said about how to handle conflicts, naming, restrictions, etc. In...

Nick Jensen wrote: > While I agree that the XDG standard is confusing and it's difficult to > know what to put where, I would think that this could safely...

Have you tried running configure without an argument? You could also try using vim_cv_timer_create_with_lrt

What if you run configure without an argument? What about using "make distclean" first. Generally, after syncing to head, "make distclean" might be needed, because the configure checks may need...