From aa44841315cad57120796999dc86c867a4133b78 Mon Sep 17 00:00:00 2001 From: Robert Siemborski Date: Mon, 17 Jul 2000 02:54:17 +0000 Subject: [PATCH] cleaned up BUGS so open bugs were separate from closed ones git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@108 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- BUGS | 37 ++++++++++++++++++++----------------- 1 file changed, 20 insertions(+), 17 deletions(-) diff --git a/BUGS b/BUGS index d91bcf73..418a027c 100644 --- a/BUGS +++ b/BUGS @@ -1,13 +1,7 @@ -- Marked cutting sometimes leaves a newline in the file unintelligently, - such as when all of a line is selected but the mark doesn't proceed to - the new line. (8) { Is this an issue? compare to pico 3.5 } - Certains are not lined up properly when there are tabs in them at certain col values. (9) [FIXED] - edit_refresh() and update_line() do not handle selecting text when the cursor is beyond COLS (10) [FIXED] -- no way to do a replace with the empty string. (11) -- Spelling support is not elegant like pico's integration of the 'spell' - program. Nano only uses ispell (for now) (12) - Moving to the end of a line when close to a multiple of COLS and at least COLS * 2 does not make the screen jump early like it would for if we were around COLS (bugs in edit_refresh, update_line) (13) @@ -17,19 +11,11 @@ (14) [FIXED, mostly] - Doing a replacement of a substring of the replace string (e.g. replacing "ed" with "fred" causes an infinite loop. (15) [FIXED] -- Cutting a file with marked text and both marker ends on the same line - causes a random segfault (16) - Cutting more than one line resets the KEEP_CUTBUFFER flag in 0.9.3 Error is in bitwise assignment (nano.h). (17) [FIXED] -- The wrapping code does not work right for lines like the following: - * * - Error is in do_wrap, must be rewritten (18). -- Wrapping a line with autoindent mode sometimes causes a segfault (19). - Nano fails to follow symlinks, even though -l isn't being used (20). [Bug in global flag init, FIXED] - When using --help or --version, the SIGINT character gets lost. (21) [FIXED] -- When inserting files, the display sometimes fails to display properly - until a pageup/down occurs (22). - edit_refresh() and update_line() (and related functions), have trouble when a tab is the character that is the boundry at COLS (23) [FIXED] - there is an off-by-one error in keeping track of totsize. It is caused @@ -37,9 +23,6 @@ but we do not, in fact, display this newline. This should go away implicitly when the "Magic Line" returns, but it is noted here for documentation's sake. (24) [FIXED] -- totsize becomes incorrect after word-wrapping (25) -- In search/replace code there is too much refreshing in bottomwin (26) -- In replace, there is no way to accept the default replace string. (27) - In replace with completely adjacent strings, every other search string will be missed (try replace ':' in a string like ':::::::::') (28) [FIXED] - If nano opens a read-only file with the --tempfile option, and a change @@ -47,3 +30,23 @@ a dialog about not being able to write the file, and it will not let the user exit (29, discovered by Joshua Jensen) [FIXED mostly] +** Open BUGS ** + +- Marked cutting sometimes leaves a newline in the file unintelligently, + such as when all of a line is selected but the mark doesn't proceed to + the new line. (8) { Is this an issue? compare to pico 3.5 } +- no way to do a replace with the empty string. (11) +- Spelling support is not elegant like pico's integration of the 'spell' + program. Nano only uses ispell (for now) (12) +- Cutting a file with marked text and both marker ends on the same line + causes a random segfault (16) +- The wrapping code does not work right for lines like the following: + * * + Error is in do_wrap, must be rewritten (18). +- Wrapping a line with autoindent mode sometimes causes a segfault (19). +- When inserting files, the display sometimes fails to display properly + until a pageup/down occurs (22). +- totsize becomes incorrect after word-wrapping (25) +- In search/replace code there is too much refreshing in bottomwin (26) +- In replace, there is no way to accept the default replace string. (27) + -- 2.39.5