You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Davis 44d2fc2ab3 Commit an undo checkpoint before each write (#11062) ... This fixes the modification indicator when saving from insert mode with a config such as [keys.insert] C-s = ":write" Previously the modification indicator would be stuck showing modified even if the buffer contents matched the disk contents when writing after some changes in insert mode with this binding. In insert mode we do not eagerly write undo checkpoints so that all changes made become one checkpoint as you exit insert mode. When saving, `Document`s `changes` `ChangeSet` would be non-empty and when there are changes we show the buffer as modified. Then switching to normal mode would append the changes to history, bumping the current revision past what it was when last saved. Since the last saved revision and current revision were then unsynced, the modification indicator would always show modified. This matches [Kakoune's behavior]. Kakoune has a different architecture for writes but a very similar system for history, transactions and undo checkpoints (what it calls "undo groups"). Upon saving Kakoune creates an undo checkpoint if there are any uncommitted changes. It does this after the write has gone through since its writing system is different. For our writing system it's cleaner to make the undo checkpoint before performing the save so that the history revision increments before we send the save event. [Kakoune's behavior]: 80fcfebca8/src/buffer.cc (L565-L566)		4 months ago
..
src	Commit an undo checkpoint before each write (#11062)	4 months ago
tests	refactor(commands): trim end of `pipe`-like output (#10952)	4 months ago
.gitignore	Initial import.	5 years ago
Cargo.toml	build(deps): bump the rust-dependencies group with 5 updates (#11113)	4 months ago
build.rs	Add icon to Windows executable (#9104)	10 months ago