Command issue - vi

[William, Lin]

Hello

I got an issue when typing vi command on oss - see blow log

Appreciate your advice

/$ vi
Visual needs addressible cursor or upline capability
:

Thanks

will @laba

[DerekW]

Not sure what problem is but "vim" is much better, Not sure if
Installed by default or have to download from ITUGLIB.

Also term should be "tn6530-8"
Can find out by "echo $TERM"

Then works great "vim", Can use Arrow keys to move around.

Derek

[wbreidbach]

vi does not run on 6530, only on VTnnn

[Joachim Schmitz]

William, Lin wrote:
> Hello
>
> I got an issue when typing vi command on oss - see blow log
>
> Appreciate your advice
>
> /$ vi
> Visual needs addressible cursor or upline capability

You need a) use a vt100 (or compatible, eg. vt320) terminal emulater (PuTTY
for example or a VTxxx session on OutsideView or MR6530) and b) tell the
shell about it via the TERM environment variable:

export TERM=vt100
or
export TERM=xterm

The latter woks better with the ITUGLIB OpenSource stuff and is identical
for the HP provided OSS stuff

bye, Jojo

[Joachim Schmitz]

DerekW wrote:
> On Mar 30, 9:15 am, "William, Lin" <cdyj...@msn.com> wrote:
>> Hello
>>
>> I got an issue when typing vi command on oss - see blow log
>>
>> Appreciate your advice
>>
>> /$ vi
>> Visual needs addressible cursor or upline capability
>>>
>>
>> Thanks
>>
>> will @laba
>
> Not sure what problem is but "vim" is much better, Not sure if
> Installed by default or have to download from ITUGLIB.

It is not, so you have to get it from ITUGLIB

> Also term should be "tn6530-8"

Won't work with vi. Use vt100 or xterm.
It does, much to my surprise, partly work with vim. But no curser keys...

For vim you may use xterm-color (vi won't work with this) and you'd get
colored syntax highlighting (if enabled, via ":syntax enable")

I use
alias vim="TERM=xterm-color /usr/local/bin/vim"
and have "syntax enable" im ~/.vimrc

> Can find out by "echo $TERM"
>
> Then works great "vim", Can use Arrow keys to move around.

Amongst other goodies ;-)

> Derek

bye, Jojo

[William, Lin]

On 3月30日, 下午4时49分, "Joachim Schmitz" <nospam.j...@schmitz-digital.de>
wrote:

You are correct, someone changed the /etc/profile and set the
TERM=t6530x that caused this issue

By the way, do you know the way to set up my custom profile and have
it loaded automatically like /etc/profile during my logon?

Thanks

will @Laba

[Joachim Schmitz]

Might have better luck with
TERM=t653x
i.e. without that 0. That one at least exists in /etc/termcap (but would
still not work with vi)

> By the way, do you know the way to set up my custom profile and have
> it loaded automatically like /etc/profile during my logon?

put ypur personal customizations into "~/.profile", i.e. the file named
".profile" in your $HOME directory. (if that is in /G/vol/subvil, you can
drop the leading '.')

Bye, Jojo

[William, Lin]

On 4月11日, 下午3时57分, "Joachim Schmitz" <jojo.nos...@schmitz-digital.de>
wrote:
> William, Lin wrote:
> > On 3ÔÂ30ÈÕ, ÏÂÎç4ʱ49·Ö, "Joachim Schmitz"

My $home directory is on a vitural volume - it says cannot find that
file though I already put it there

Thanks

will @ laba

[ghr]

OSS does not know about virtual volumes ie they mix as well as oil and
water.

[Joachim Schmitz]

William, Lin wrote:
> On 4?11?, ??3?57?, "Joachim Schmitz" <jojo.nos...@schmitz-digital.de>
> wrote:
>> William, Lin wrote:
>>> On 3月30日, 下午4时49分, "Joachim Schmitz"

Accessing files on virtual volumes is not supported by OSS

get yourself an 'initial -direcory' configured in safeguard
or make sure the guardian default is on a physical volume

Bye, Jojo

[William, Lin]

On 4月11日, 下午8时11分, "Joachim Schmitz" <jojo.nos...@schmitz-digital.de>

wrote:
> William, Lin wrote:
> > On 4?11?, ??3?57?, "Joachim Schmitz" <jojo.nos...@schmitz-digital.de>
> > wrote:
> >> William, Lin wrote:

> >>> On 3ÔÂ30ÈÕ, ÏÂÎç4ʱ49·Ö, "Joachim Schmitz"

Thank you

_