Fixup f4364c75: remove two more Update::SinglePar instances

They do not do what the author(s) of these lines thought it would do,
and can create crashes.

(cherry picked from commit 485f5afc21)
This commit is contained in:
Jean-Marc Lasgouttes 2024-07-20 17:12:09 +02:00
parent 5ba197d2f6
commit 0867aaf5c5
2 changed files with 4 additions and 4 deletions

View File

@ -5266,7 +5266,7 @@ void Text::dispatch(Cursor & cur, FuncRequest & cmd)
// Set the cursor
bvcur.resetAnchor();
if (!bv->mouseSetCursor(cur, cmd.modifier() == ShiftModifier))
cur.screenUpdateFlags(Update::SinglePar | Update::FitCursor);
cur.screenUpdateFlags(Update::FitCursor);
// FIXME: move this to mouseSetCursor?
if (bvcur.wordSelection() && bvcur.inTexted())
expandWordSel(bvcur);
@ -5365,9 +5365,7 @@ void Text::dispatch(Cursor & cur, FuncRequest & cmd)
// selectWord but bvcur is current
// mouse position.
cur.bv().cursor().setSelection();
// We might have removed an empty but drawn selection
// (probably a margin)
cur.screenUpdateFlags(Update::SinglePar | Update::FitCursor);
cur.screenUpdateFlags(Update::FitCursor);
} else
cur.noScreenUpdate();
// FIXME: We could try to handle drag and drop of selection here.

View File

@ -55,6 +55,8 @@ What's new
- Fix crash when attempting to search in selection that contains only math.
- Fix potential crashes when scrolling documents.
- Fix bug where the dialog asking for saving unapplied changes on buffer change
popped up twice, or sometimes not at all (bug 12954).