bfredl

For better and worse, this is how window options in vim and neovim works. The default options for a buffer is set by the current or last window that displayed...

> This is not how window options in vim and neovim works. A option that local to window is bound to (winid, buffer number) pair, the option set for (winid1,...

But as far for _adding_ a new option mode to keep options private to a window (and never have them leak to another window), we could consider that. Though there...

> Some discussions in this issue. Exactly how the presence of "some discussion" with multiple different standpoints a conclusive argument for anything? > doc is referred by the discussion. This...

Sorry, I meant `cursorline` but either set or setl is fine. (statusline is global-local and thus has another set of different behaviors...)

@lacygoill Right, that seems to be consistent with the implementation `find_wininfo()` and `get_winopts()`. The order in which entries are added to `buf->b_wininfo` seems somewhat arbitrary (it is created for first...

Nice work! Only glitch I noticed so far: with `set wrap list`, and using C-E/C-Y scrolling (and narrow screen so that most lines are wrapped), every screenline gets prepended by...

> if you view one line longer than the entire screen and the cursor past the first screen's worth of characters. The fix is pretty simple (just check that row==0...

I don't think `` and `` in particular have been tested much, rather just scrolling that results from cursor movement ( i e `j`, `k`, `[N]G` and so forth).

Nice, I will take a look. > I've made this buffer-local, even though it might initially seem to be more related to windows than buffers. My reasoning is that I...