1
1

Adding a note to the documentation about undo not working after

a justification or reindentation.


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@5475 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
Этот коммит содержится в:
Benno Schulenberg 2015-12-03 09:34:10 +00:00
родитель 4bc8ff1e6d
Коммит ccc9b24f16
3 изменённых файлов: 19 добавлений и 1 удалений

Просмотреть файл

@ -7,6 +7,8 @@
* src/text.c (do_indent): Also here discard the entire undo stack, to
prevent nano from making mistakes when trying to undo edits after an
indentation change. This works around Savannah bug #46591.
* doc/man/nano.1, doc/texinfo/nano.texi: Add a note about undo not
working after a justification or reindentation.
2015-12-02 Benno Schulenberg <bensberg@justemail.net>
* doc/syntax/python.nanorc: Don't colour triple quotes by themselves.

Просмотреть файл

@ -275,7 +275,13 @@ it unique. In multibuffer mode, \fBnano\fP will write all the open
buffers to their respective emergency files.
.SH BUGS
Please report any bugs that you encounter via
Justifications (\fB^J\fR) and reindentations (\fBM-{\fR and \fBM-}\fR)
are not yet covered by the general undo system. So after a justification
that is not immediately undone, or after any reindentation, earlier edits
cannot be undone any more. The workaround is, of course, to exit without
saving.
.sp
Please report any other bugs that you encounter via
https://savannah.gnu.org/bugs/?group=nano.
.SH HOMEPAGE

Просмотреть файл

@ -386,6 +386,7 @@ Ignored, for compatibility with Pico.
* The Statusbar::
* Shortcut Lists::
* Using the Mouse::
* Limitation::
@end menu
@node Entering Text
@ -490,6 +491,15 @@ Shift key during those actions.
The mouse will work in the X Window System, and on the console when gpm
is running.
@node Limitation
@section Limitation
Justifications (@code{^J}) and reindentations (@code{M-@{} and @code{M-@}})
are not yet covered by the general undo system. So after a justification
that is not immediately undone, or after any reindentation, earlier edits
cannot be undone any more. The workaround is, of course, to exit without
saving.
@node Built-in Help
@chapter Built-in Help