[konsole] [Bug 452476] Behaviour of ansi control sequences after sixel graphic depends on how much lines were already written before the program started.

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=452476

Kurt Hindenburg <kurt.hindenburg at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util
                   |ities/konsole/commit/9ae57f |ities/konsole/commit/ad1421
                   |4e1de920d1a30b8f64448fd6c18 |f8b87b219d38f08d7ba794fe2f4
                   |6a36730                     |addd75d

--- Comment #6 from Kurt Hindenburg <kurt.hindenburg at gmail.com> ---
Git commit ad1421f8b87b219d38f08d7ba794fe2f4addd75d by Kurt Hindenburg, on
behalf of Matan Ziv-Av.
Committed on 19/04/2022 at 18:40.
Pushed by hindenburg into branch 'master'.

Fix cursor position after drawing Sixel graphics

Moving all cursor and scroll handling to addPlacement.

This requires the moveCursor parameter to have three possible values,
since Sixel cursor movement is not the same as Kitty/iterm2. This also
unnecessitates addPlacement return value.
(cherry picked from commit 9ae57f4e1de920d1a30b8f64448fd6c186a36730)

M  +19   -21   src/Screen.cpp
M  +14   -14   src/Screen.h
M  +1    -6    src/Vt102Emulation.cpp

https://invent.kde.org/utilities/konsole/commit/ad1421f8b87b219d38f08d7ba794fe2f4addd75d

-- 
You are receiving this mail because:
You are the assignee for the bug.