UNIX for Dummies Questions & Answers

it didn't find -L option for file in Sunos so i runned below

Code:

file -h `which vim`
The result is 
/tools/local/bin/_SOLARIS2.7_sun4d/bin/vim:      executable /bin/ksh script

Before i am using vi editor and i moved to vim for better syntax view.
i had an alias for vi as
alias vi=vim in my profile .

Not sure still it is give '0' after i exit by file

0/tools/emp002198/lib/dc>

Yes, vim is better (IMO) than some old vi version, so (I think) you made the right move.

It's saying vim is a shell script in a "local" bin directory!

What happens when you run:

Code:

 vim /tools/local/bin/_SOLARIS2.7_sun4d/bin/vim

Can you view it? Is it a shell script? If so, look for the part where it runs the vim executable, and what happens after running the executable. You won't hurt anything.

Another option is to run the following to find the real vim executable:

Code:

find / -name "vim" -print 2> /dev/null > temp.x; vim temp.x

when i opened the file it has

Code:

#! /bin/ksh
BASEDIR=`dirname $0`
# echo "VIM=$BASEDIR/vim-5.5/runtime $BASEDIR/vim_exe $@"
VIM="$BASEDIR/vim-5.5/runtime" VIMRUNTIME=$VIM $BASEDIR/vim_exe $@
# echo "param $@"

if i gave which vim_exe the result is

/tools/local/bin/_SOLARIS2.7_sun4d/bin/vim_exe

That looks pretty innocent. Nothing there seems to be responsible for printing that extra 0 character.

The script sets two environment variables VIM and VIMRUNTIME at the same time running the real vim (vim_exe) with the files that you provided on command line ($@).

I would again try "file /tools/local/bin/_SOLARIS2.7_sun4d/bin/vim_exe" to make sure that really is the executable (just a reality check).

Then, you could try running the /tools/local/bin/_SOLARIS2.7_sun4d/bin/vim_exe file and see what happens when you exit out the way you did before. My guess is you will still see the extra 0 but it's worth trying.

When you run vim_exe directly, without VIM and VIMRUNTIME set, vim possibly will not run perfectly (for example, vim might not be able to find help files). That's why the sysadmin set up the shell script wrapper. But it might work well enough for the test. It's worth trying to run vim_exe and see if 0 still appears when you quit.

Yes i tried that too...
Vim gave some some help files not present ... and while existing it gain gave the '0'

Code:

0/home/amp002198>

---------- Post updated at 06:47 AM ---------- Previous update was at 06:41 AM ----------

i have vim version 5.5
/tools/local/bin/_SOLARIS2.7_sun4d/bin/vim-5.5/

vim version 5.5 is from 1999! That is pretty old.

On the other hand, it should still work. vim was stable back in 1999. You could request a newer version, and who knows, that might fix the problem. That would be a reasonable request. However, we would lose the satisfaction of figuring out the actual detailed cause.

It seems odd to me, not only does it print 0 but does NOT print a newline. For example, compare the following commands:

Code:

$ echo 0
0
$ echo -n 0
0$

Can you try it on some other computers around there? If the problem occurs on different monitors or environments, then vim is producing the extra 0. But if you can find even ONE other computer that does not produce the extra 0, I think that's strong evidence the problem is not vim, but instead might be something with your $TERM or other such display setting.

i tried but no luck....
the same issue