PROBLEM:  (UVO104615 QAR 44614 QAR 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.


FILE(s):

/usr/bin/ex    		            subset OSFBASE410
CHECKSUM: 07506    288     RCSfile: ex.c      RCS: 4.3.32.2
ex_temp.h      Revision: 4.2.7.3
ex_addr.c      Revision: 4.2.9.4
ex_re.h        Revision: 4.2.7.3
ex_cmds.c      Revision: 4.3.25.2
ex_temp.h      Revision: 4.2.7.3
ex_cmds2.c     Revision: 4.2.9.4
ex_temp.h      Revision: 4.2.7.3
ex_cmdsub.c    Revision: 4.2.19.3
ex_temp.h      Revision: 4.2.7.3
ex_data.c      Revision: 4.2.7.2
ex_extern.c    Revision: 4.2.7.2
ex_re.h        Revision: 4.2.7.3
ex_temp.h      Revision: 4.2.7.3
ex_get.c       Revision: 4.2.7.2
ex_io.c        Revision: 4.4.34.2
ex_temp.h      Revision: 4.2.7.3
ex_put.c       Revision: 4.2.10.5
ex_re.c        Revision: 4.2.9.7
ex_re.h        Revision: 4.2.7.3
ex_set.c       Revision: 4.2.7.3
ex_temp.h      Revision: 4.2.7.3
ex_subr.c      Revision: 4.3.9.4
ex_re.h        Revision: 4.2.7.3
ex_temp.c      Revision: 4.3.12.5
ex_temp.h      Revision: 4.2.7.3
ex_tty.c       Revision: 4.2.7.3
ex_unix.c      Revision: 4.2.7.4
ex_temp.h      Revision: 4.2.7.3
ex_v.c         Revision: 4.2.7.3
ex_re.h        Revision: 4.2.7.3
ex_vadj.c      Revision: 4.2.7.2
ex_vget.c      Revision: 4.2.14.4
ex_vmain.c     Revision: 4.2.13.2
ex_voper.c     Revision: 4.2.7.4
ex_vops.c      Revision: 4.2.9.2
ex_vops2.c     Revision: 4.2.11.2
ex_vops3.c     Revision: 4.2.7.4
ex_vput.c      Revision: 4.2.9.2
ex_vwind.c     Revision: 4.2.7.2
ex_crypt.c     Revision: 4.2.5.4
ex_temp.h      Revision: 4.2.7.3
/usr/bin/edit
CHECKSUM: 07506    288
/usr/bin/vedit
CHECKSUM: 07506    288
/usr/bin/vi
CHECKSUM: 07506    288
/usr/bin/view
CHECKSUM: 07506    288

