bfredl
bfredl
> let's consider undo/redo out of scope, they aren't useful in prompt buffers afaik. An alternative would be to allow undo but delete the past undo history at submission (or...
yeah, the existing behavior is not "wrong" (there is no rule against overlong MSGPACK encodings) but this saves a byte in a lot of common cases, so let's do it.
`default_colors_set` should probably include flag dict already (kinda "colors" if not strictly "colors")
I don't think it should scroll automatically but there should be an extended API interface for scrolling which is fully aware of filler/virtual lines as well as skipcol.
> Isn't this the same as "the line should be invisible by default", even though it just got added by an API call? No. > you can't do it with...
> I would at least expect (and maybe even gg) to scroll up to the virtual lines. How would an API resolve that? The API would resolve what people was...
> . The original issue is that virt_lines with virt_lines_above do not show on row 0 without pressing (or ). Your response implies this is resolved with an API which...
@andmis hmm that would make sense. actually the behavior of `nvim_buf_set_lines` is a bit strange, sometimes it scrolls up even if that doesn't help the added top line to be...
> Is the default, "must be focusable", wrong for getmousepos()? Should/can it be changed? The default is correct. "focusable" actually means "focusable" which includes both keyboard and mouse. fine as...
Not in #2077 #2244, but I plan to work on it after those are done (they are quite big PR:s already)