diff options
| author | Kaz Kylheku <kaz@kylheku.com> | 2020-08-14 06:59:35 -0700 |
|---|---|---|
| committer | Kaz Kylheku <kaz@kylheku.com> | 2020-08-14 06:59:35 -0700 |
| commit | 7bd54dd6ecb2c7e1f9da760bbf4645af5f546d96 (patch) | |
| tree | 51647ba8bbf8cb2792adb210ea07cbf8e70ebfb3 /txr.1 | |
| parent | 658f7fe362dbce165e150482eda1cbd54ef66f40 (diff) | |
| download | txr-7bd54dd6ecb2c7e1f9da760bbf4645af5f546d96.tar.gz txr-7bd54dd6ecb2c7e1f9da760bbf4645af5f546d96.tar.bz2 txr-7bd54dd6ecb2c7e1f9da760bbf4645af5f546d96.zip | |
doc: listener: undo over history clarifications.
* txr.1: Document that all the edits done to a history line
are committed as a single undo item when navigating away from
it. Clarify some text related to undo over a history line.
Diffstat (limited to 'txr.1')
| -rw-r--r-- | txr.1 | 18 |
1 files changed, 12 insertions, 6 deletions
@@ -74126,9 +74126,15 @@ up/down arrow keys or a navigation command is used to show a different history line, or to restore the original current line, then the edit is made permanent: the edited line replaces its original version in the same position in the history. This feature allows corrections to be made to the -history. However, if a recalled line is edited and submitted without -navigating to another line, then it is submitted as a newly composed line, -without replacing the original in the history. +history. + +The edit is recorded in the line's undo history as a single change; if the +edited line is visited again, then a single Ctrl-O command will revert all the +edits that were made. + +However, if a recalled line is edited and submitted without navigating to +another line, then it is submitted as a newly composed line, without replacing +the original in the history. Each submitted line is entered into the history, if it is different from the most recent line already in history. This is true whether it @@ -74356,9 +74362,9 @@ There is no redo. When undo removes an edit to restore to a prior edit state, the removed edit is permanently discarded. Note that if undo is invoked on a historic line, each undo step updates that -history entry instantly to the restored state. This is in contrast -to the way new edits work. New edits are not committed to history until -navigation takes place to a different history line. +history entry instantly to the restored state, not only the visible edit +buffer. This is in contrast to the way new edits work. New edits are not +committed to history until navigation takes place to a different history line. Also note that when new edits are performed on a historic line and it is submitted with Enter without navigating to another line, the undo information |