The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
| Version |
Location |
Description |
Submitted By |
Corrected |
| Printed |
Page 33
table 2-4 |
"Editing Action" for "Command" `A' is wrong:
Append text at beginning of line
It shoud read
Append text at end of line
instead.
|
Anonymous |
|
| Printed |
Page 33
Table 2-4, line 4 |
Text says "A will cause append at beginning of line". Shouldn't this be "A will cause append at end of line"? (At least my VIM 7.2 on Windows works that way.)
Note from the Author or Editor:
the reviewer's comments are correct.
change the table entry text for the entry "A" (capital A) from:
Append text at beginning of line
to:
Append text to end of line
|
Thomas Spence |
|
| Printed |
Page 36
First example of the "z" command in the "Repositioning the Screen with z" section |
Very minor.
The examples for z call out "Enter", ".", and "-". For completeness(symmetry?), I would suggest noting that "+" is a synonym for "Enter".
Note from the Author or Editor:
change the entry for:
z [ENTER]
by additionally adding:
z+
resulting in:
z[ENTER]
z+
|
Anonymous |
|
| Printed |
Page 38
Text under second example in the "Movement on the current line" section |
A nit, really.
The "n|" will just move to the end of the line (as opposed to adding spaces to the end) if the number, "n", is greater than the number of characters on the line.
I suppose this should be obvious but it does surprise some when they encounter it for the first time.
|
Anonymous |
|
| Printed |
Page 50
Fifth line of text |
The text states two ways to override the view mode by adding an exclamation point to the write command.
The second example should be followed by the punctuation. It should be ":wq!", not ":wq"
|
Anonymous |
|
| Printed |
Page 85 f.
Examples 12 and 13 |
While the problem with example 12 is that the given solution is just not optimal, the problem with example 13 is that the given solution is wrong.
Example 12
----------
Using
:%s/^ *//
instead would achieve the same task faster and IMHO cleaner.
Example 13
----------
The given solution
:%s/\(.*\) *$/\1/
does _not_ delete all spaces at the end of every line; since * is a greedy quantifier and the regex is parsed left to right, only one space at the end is deleted.
My favourite solution would be
:%s/ *$//
instead.
Note from the Author or Editor:
reader is correct, the example 13 should be corrected per his/her instructions as example 13 is wrong.
reader is also correct that in his/her opinion the suggested alternate substitution is cleaner. however, since example 12 is ostensibly correct (it does what it says it does), leave that one unchanged.
|
Anonymous |
|
| Printed |
Page 137
table 8-7 |
For vim (and probably vor elvis, but I can't check ATM) the description of the action is wrong:
``... When set, long lines simply go off the edge of the screen. ...''
This should read:
``... When unset, long lines simply go off the edge of the screen. ...''
Note: set vs. unset.
Note from the Author or Editor:
verified this behavior as described in reviewer's comments for vim.
change "When set" in the vim table entry to "When unset"
|
Anonymous |
|
| Printed |
Page 179
heading for third paragraph |
This may be more serious, but the paragraph heading indicates a discussion of "Conditional Split Commands" -- plural. The paragraph only discusses the ':topleft cmd' command. (Although the ':vertical' command is alluded to in a table on page 186, it is not discussed here.)
|
Anonymous |
|
| Printed |
Page 181
Table 11-2 Window navigation commands |
In the fourth item from the bottom of the table, the capital W is missing from the 'Ctrl-W W' command (move to next window above or to the left).
|
Anonymous |
|
| Printed |
Page 190
Top of page - in bottom of table 11-8 - just above :bmod & :sbmod listing |
In table 11-8, the commands to "Move to last buffer" are given as
:bfirst
:sbfirst
(These are listed in two places, correctly for the first instance, but incorrectly for the second instance.)
Note from the Author or Editor:
the entry on p190 where description is "Move to last buffer..." should have its left-hand-side changed from:
:bfirst
:sbfirst
to:
:blast
:sblast
|
Anonymous |
|
| Printed |
Page 191
second paragraph |
Both of the first two paragraphs on this page purport to describe the 'Ctrl-W g f' command, but I believe the second one meant to be the 'Ctrl-W g F' command instead.
|
Anonymous |
|
| Printed |
Page 208
Figure 12-3 File type of new file detected AND fourth paragraph |
The '!' in '#!/bin/sh' is invisible in the grey-scale image of the figure. It is just plain missing in the discussion of this figure in the fourth paragraph. (But it is in the input instructions from paragraph 2!)
Note from the Author or Editor:
in paragraph 4 on page 208, that begins: "You can tell from the picture...", change:
"does not show that # /bin/sh is blue"
to:
"does not show that #!/bin/sh is blue"
|
Anonymous |
|
| Printed |
Page 249
Last paragraph, first sentence. |
``First, make sure to get rid of all folds by typing zD [...]''
This should be zE instead of zD.
|
Anonymous |
|
| Printed |
Page 385
Line 6, beginning from g* |
Original:
g* Search backward for .......
Correct:(Tested with VIM)
g* Search FORWARD for .......
Note from the Author or Editor:
submitted error description is correct.
correction is also correct. (though I'm sure they don't mean for "FORWARD" to be all caps, but did so for emphasis.)
|
Anonymous |
|
| Printed |
Page 421
'backspace' description |
Written :
"Values are: 0 for vi compatibility; 1 to backspace over newlines; and 2 to backspace over the start of insert.
Using a value of 3 allows both."
Actually not. There are 3 options for backspace option, which are 0, 1 and 2.
We should read :
"Values are: 0 for vi compatibility; 1 to backspace over newlines and indents; and 2 to backspace over the start of insert, newlines and indents."
There is no "3" value.
Note from the Author or Editor:
replace:
"Values are: 0 for vi compatibility; 1 to backspace over newlines; and 2 to backspace over the start of insert."
with:
"Values are: 0 for vi compatibility; 1 to backspace over newlines and indents; and 2 to backspace over the start of insert, newlines and indents."
|
Anonymous |
|
| Other Digital Version |
436
Last paragraph |
I'm Antonio Valle, the creator of the vi Powered! logo, in year 1996. I then created the Proud to Use VI page, and it was once hosted in the URL http://www.abast.es/~avalle/vi.html but we loose it in a system crash with no backups.
I just wanted to clarify that the URL in the book is incorrect, and would be very proud to appear as the original creator of the logo.
Thanks!
Antonio Valle
PS: You can confirm this information in the Darryl website, where he still has the copy of the original page (translated into english) at http://www.darryl.com/viold.html
Note from the Author or Editor:
I verified the url of the old page. In the book we do not attribute the creator but simply reference the location of the vi logo gif.
change first sentence in said paragraph from:
The original home page for the vi Powered logo was http://www.abast.es/~avelle/vi.html.
to:
The original home page for the vi Powered (created by Antonio Valle) logo was http://www.abast.es/~avelle/vi.html.
|
Antonio Valle |
|
