summaryrefslogtreecommitdiff
path: root/usr.bin/vi/docs/bugs.current
diff options
context:
space:
mode:
authorTheo de Raadt <deraadt@cvs.openbsd.org>1995-10-18 08:53:40 +0000
committerTheo de Raadt <deraadt@cvs.openbsd.org>1995-10-18 08:53:40 +0000
commitd6583bb2a13f329cf0332ef2570eb8bb8fc0e39c (patch)
treeece253b876159b39c620e62b6c9b1174642e070e /usr.bin/vi/docs/bugs.current
initial import of NetBSD tree
Diffstat (limited to 'usr.bin/vi/docs/bugs.current')
-rw-r--r--usr.bin/vi/docs/bugs.current44
1 files changed, 44 insertions, 0 deletions
diff --git a/usr.bin/vi/docs/bugs.current b/usr.bin/vi/docs/bugs.current
new file mode 100644
index 00000000000..500f3ba6d51
--- /dev/null
+++ b/usr.bin/vi/docs/bugs.current
@@ -0,0 +1,44 @@
+List of known bugs:
+
++ The number option doesn't display line numbers in ex append/insert
+ mode.
+
++ The option sidescroll is completely wrong, and setting it does more
+ harm than good.
+
++ When nvi edits files that don't have trailing newlines, it appends
+ one, regardless.
+
++ Open mode is not yet implemented.
+
++ ^C isn't passed to the shell in the script windows as an interrupt
+ character.
+
++ The options:
+
+ hardtabs, lisp, optimize, redraw, slowopen
+
+ are recognized, but not implemented. These options are unlikely to
+ be implemented, so if you want them you might want to say something!
+ I will implement lisp if anyone ever documents how it worked.
+
++ Screen repainting over slow lines, for some screen changes, isn't
+ as good as the historic vi's.
+
++ The line movement commands ('k', 'j' are easy examples) don't find the
+ most attractive cursor position correctly when wrapped lines are longer
+ than 80 characters, and they're on the second or subsequent lines.
+
++ Colon commands longer than a single line cause the display to be
+ incorrect.
+
++ The usages of S_{REDRAW,REFORMAT,REFRESH,RENUMBER,RESIZE} are
+ inconsistent, and should be reviewed. In particular, S_REFRESH
+ in any screen redraws all screens.
+
++ Historic vi permitted :g/xxx/vi, i.e. you could execute ex/vi as
+ global commands. Need to review all of the old commands to verify
+ which ones could/could not be used as global commands.
+
++ If you run out of space in the recovery directory, the recovery
+ file is left in place.