I think the nocompatible setting might have been on the right track. Some of those symptoms sound a lot like you might have had vi running instead of vim. If it was indeed vim, it may have been in vi compatibility mode.
To see the value for an environment variable, type this at the command line: echo $VARNAME where VARNAME is the name of the variable whose value you want to see. For example, to see the value of TERM, type echo $TERM. -Brent On Fri, 2003-09-12 at 09:44, john jonas wrote: > --- Phillip Hellewell <[EMAIL PROTECTED]> wrote: > > On Thu, Sep 11, 2003 at 01:59:39PM -0700, john jonas > > wrote: > > > I just did a clean install of RH 9 and vim is > > doing > > > weird stuff and I'm hoping for suggestions. I > > can't > > > get it to do syntax highlighting (:set syn=php) > > and I > > > cant split the screen (:sp file). It just sits > > there > > > when I do either of those and nothing changes. > > Any > > > suggestions? > > > > > What is your TERM environment variable set to? > > I don't know. How do I check it? > > Regardless, today when I logged into the machine vim > is working like normal. It does syntax highlighting, > splits the screen, and even remembers which line I was > editing when I last quit. > > What would cause it to behave like it was? > > Thanks for the help, > > John > > > > > -- > > Phillip Hellewell <[EMAIL PROTECTED]> > > > > ____________________ ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
