I use C-n/C-p (next-line).
> Why are you setting the breakpoint on that line?
I am trying to debug the current version w/o my patch, but probably I just messed something up. Let's ignore this I got better results.
I am using `breakpoint set -f scroll.c -l 697`.
Currently, when I have 2 panes and I have the right pane with content on it `do_direct_scrolling` doesn't go into the first condition in the loop. So, It doesn't stop in the debugger. But, when I open the scratch buffer which has only few lines and I try to scroll in the left pane on the lines where the right buffer doesn't have any content because there are only few lines in the buffer it stops:
```
(lldb) p *p
(matrix_elt) $3 = {
writecost = 35356
insertcost = 34958
deletecost = 35357
insertcount = 97
deletecount = 1
writecount = 1
}
```
... just because the cost of insertion is lower than the write cost. Then I set the breakpoint into different line set the right window a buffer with content:
```
(lldb) breakpoint set -f scroll.c -l 688
```
So, I see
```
(lldb) p *p
(matrix_elt) $4 = {
writecost = 54426
insertcost = 54996
deletecost = 54735
insertcount = 1
deletecount = 8
writecount = 148
}
```
Insert and delete cost are greater than write cost.
I see the behavior as a correct one (at least by design), but when we do insert instead of writing the terminal flickers. Do we need to adjust some numbers or do we have to understand the reason why we flush the content?