Vincent Ging Ho Yim 96e73bdadd cli undo: detect "double undo" from operation metadata instead ...

To identify an `undo` operation, checking that the views of the "bad" op and its
grandparent are equal is necessary but not sufficient. For example, creating a bookmark
and then immediately deleting it also "resets" the view. This commit fixes this by also
checking the "description" in the operation metadata to identify "double undo" properly.

With this commit, the "double undo" warning is now shown whether users undid the latest
undo implicitly (with `jj (op) undo`) or explicitly (with `jj (op) undo <op set>` or `jj
(op) undo @`).

If undoing an older undo (prior to `@`), the warning is not shown.

2025-05-21 13:20:10 +00:00

..

examples

backend: make read_file() return a AsyncRead

2025-05-20 13:23:36 +00:00

src

cli undo: detect "double undo" from operation metadata instead

2025-05-21 13:20:10 +00:00

testing

diff: Run external diff tools in their temp dir

2025-05-12 21:34:19 +00:00

tests

cli undo: detect "double undo" from operation metadata instead

2025-05-21 13:20:10 +00:00

build.rs

build: fix cargo publish by symlinking cli/docs->docs

2024-11-05 17:37:14 -08:00

Cargo.toml

backend: make read_file() return a AsyncRead

2025-05-20 13:23:36 +00:00

docs

build: fix cargo publish by symlinking cli/docs->docs

2024-11-05 17:37:14 -08:00

LICENSE

cargo: add LICENSE file to each crate we publish

2023-09-22 21:48:28 -07:00