PROBLEM: (UVO104615, QAR 44614, 47303) (Patch ID: OSF410-400204) ******** Blank lines in the .exrc file prevent the vi editor from executing. To recreate this problem, create a .exrc file in your home directory. Leave a blank line at the end of the .exrc file. Enter the vi command; vi will exit immediately and your terminal window will display the shell prompt. PROBLEM: (QAR 39453) (Patch ID: OSF410-400204) ******** The ex editor does not properly manage the file name buffers when a "write append" command fails. For example, prior to invoking the ex editor, assume file "a" does not exist, but file "b" does. Run ex without specifying a file name, enter some characters and try to get ex to output these characters in append mode in append mode to a file that does not exist. After it correctly reports "no such file or directory", specify a file that does exist. For example: systema> ex :a hello worlds . :w No current filename :w >> a "aa" No such file or directory :w >> b "b" 3 lines, 12 characters When you try to exit the file, ex will write to the wrong file. :e b No write since last change (:edit! overrides) #>-- won't do it :xit #<-- Let's quit "a" [New file] 3 lines, 12 characters #>-- ok, I'll write for you systema> The problem is that ex creates a new file when it should not. After applying this patch, the ex editor will provide the following error message: No current file name PROBLEM: (QAR 46284) (Patch ID: OSF410-400204) ******** The vi editor may erroneously report a "Bad file number" error message when switching between files. For example, if file "xx" has access privileges of -r--r--r--(no write enabled) and file "yy" has privileges of -rw-r--r-- (write enabled), the following ort example will cause vi to report "Bad file number": vi xx yy :n Shift+Ctrl+^ dd :w Shift+Ctrl+^ :e! "xx" [Read only] Bad file number Shift+Ctrl+^ "yy" Bad file number After applying this patch, the "xx" file is reported to be read-only and the write will fail. The "yy" file, will be written with no error message. error message. PROBLEM: (HPAQ50F34, QAR 53388, 54361) (Patch ID: OSF410-114) ******** This patch fixes a problem that causes the vi command to core dump. The problem occurs if one line is yanked into a named buffer. For example, the following command, which should mark the current line and copy the line into buffer "a", will generate a core dump: may'a PROBLEM: (QAR 53323, 45227) (Patch ID: OSF410-121) ******** This patch fixes a problem in which the vi command, "ce", does not work as expected. For example, when the cursor is on the beginning of the word "name", typing "ce" should place a dollar sign ($) over the letter "e": nam$\n", ^ cursor is here, type "ce" Instead, the vi command "ce" places the dollar sign at the end of the line, over the comma: name\n"$ ^ cursor is here, type "ce" PROBLEM: (QAR 58706) (Patch ID: OSF410-405327) ******** This patch fixes a problem with the vi editor environment variable EXITIT that occurs when EXINIT includes the editors so subcommand. When EXINIT included an so subcommand for a file which itself contained an so subcommand to a second file, the editor would exit without an error message whenever the second file did not exist. PROBLEM: (EVT102588, QAR 37163) (Patch ID: OSF410-405475) ******** This patch corrects the following two problems which can occur when using vi to edit files 100MB or larger; o The terminal settings can be disrupted causing the window to be un-usable. o A core dump may occur. PROBLEM: (CLD HPAQ9049V, QAR 55075) (Patch ID: OSF410-405510) ******** This patch fixes a problem where vi puts the server port into PASSALL MODE (where XON/XOFF is no longer effective). This creates garbage in the file.