[VIM] VMS version doesn't do logicals?
Uncle Jeff
www.polarfox.com.
I was using version 4.5 for quite a while (where I got the binary, I
can't remember), and all was a-ok. Now after I've upgraded it seems
that vim scrambles the logical values I pass to it, so I can only open
files in my working directory.
For example, we have the following system logical defined to point to
part of our source tree:
DEVAXP:[SRC]> sh log system$dvsrc
"SYSTEM$DVSRC" = "DISK3:[FI.SRC.DV.SYSTEM]" (LNM$SYSTEM_TABLE)
Now, if I either pass a file name as a command line argument _or_
try to open a file after vim is opened, like so:
vim system$dvsrc:start.p
The file name gets mangled exactly like so:
systemDISK3:[FI.SRC.DV]start.p
After vim is opened, I _can_ open the file if I use unix-like syntax:
:vi /disk3/fi/src/dv/system/start.p
But that is a pain. Like I said, it worked in the 4.5 version I was
using before. Any ideas?
--
( >- THKS %^>
/~\ Uncle Jeff (get rid of JUNK to email)
| \) Jeff.Ho...@JUNKfederated.ca
\_|_ Linux, the choice of a GNU generation
Sent via Deja.com
http://www.deja.com/
JF Mezei
> DEVAXP:[SRC]> sh log system$dvsrc
> "SYSTEM$DVSRC" = "DISK3:[FI.SRC.DV.SYSTEM]" (LNM$SYSTEM_TABLE)
> vim system$dvsrc:start.p
> The file name gets mangled exactly like so:
> systemDISK3:[FI.SRC.DV]start.p
Prior to calling vim, do the following:
SHOW DEFAULT. (the unix equivalent of pwd).
You might want to SET DEF SYSTEM$DVSRC prior to invoking "vim".
Also, you might want to find our exactly what "vim" is.
$SHOW SYMBOL vim might reveal it is a command procedure which you could list
to see what it does. Maybe it is the one which puts you in a different directory.
if vim is not a symbol, then it is a installed as a command and thus you can't
do much about it.
Uncle Jeff
JF Mezei <jfmezei...@videotron.ca> wrote:
> Uncle Jeff wrote:
>> DEVAXP:[SRC]> sh log system$dvsrc
>> "SYSTEM$DVSRC" = "DISK3:[FI.SRC.DV.SYSTEM]" (LNM$SYSTEM_TABLE)
>> try to open a file after vim is opened, like so:
>> vim system$dvsrc:start.p
>> The file name gets mangled exactly like so:
>> systemDISK3:[FI.SRC.DV]start.p
>
> Prior to calling vim, do the following:
> SHOW DEFAULT. (the unix equivalent of pwd).
>
> You might want to SET DEF SYSTEM$DVSRC prior to invoking "vim".
That's what I have to do now. As long as the file is in the current
directory, then I can open it just fine.
> Also, you might want to find our exactly what "vim" is.
> $SHOW SYMBOL vim might reveal it is a command procedure which you could list
> to see what it does. Maybe it is the one which puts you in a different directory.
>
> if vim is not a symbol, then it is a installed as a command and thus you can't
> do much about it.
Yes, vim is an installed program. I should know, I installed it
myself! ;&>. I know the problem is with the program itself, because
other programs, like the tpu editor, translate the logicals just fine.
I was hoping there might be others out there who've used vim
succesffuly in vms, who might know a fix for this. Thanks anyway, JF.
Robert Deininger
>
> I was hoping there might be others out there who've used vim
> succesffuly in vms, who might know a fix for this. Thanks anyway, JF.
>
I'm apparently the inheritor of a TPU-based vi. It works quite well on VAX and alpha. It adds quite a bit to vi. I duuno how it compares to vim, which I've never used.
I've offered once or twice to kit it up for the freeware. I received no response, so I haven't made in progress in that direction.
--
Robert Deininger
rdein...@mindspring.com
Hoff Hoffman
:I've offered once or twice to kit it up for the freeware.
Apologies on my clear lack of responsiveness. I had previously snagged
a copy of VIM-SAVESET.ZIP dated 7-Feb-2000 for inclusion on the next
Freeware (V5), containing VIM.SAVESET also dated 7-Feb-2000. Is that
the current/correct kit?
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoffman#xdelta.zko.dec.com
Robert Deininger
> In article <rdeininger-29...@user-2ivec43.dialup.mindspring.com>, rdein...@mindspring.com (Robert Deininger) writes:
> :I've offered once or twice to kit it up for the freeware.
> :I received no response, so I haven't made in progress in that direction.
>
> Apologies on my clear lack of responsiveness. I had previously snagged
> a copy of VIM-SAVESET.ZIP dated 7-Feb-2000 for inclusion on the next
> Freeware (V5), containing VIM.SAVESET also dated 7-Feb-2000. Is that
> the current/correct kit?
Umm, that wouldn't be me. I'm in no way a keeper of VIM.
The thing I've been using the past decade or so is almost pure TPU. It was written by Gregg Wonderly, formerly of OK State University. Past attempts to find him failed.
Today I tried to find a current email address for him, to ask about submitting his vi. I didn't find him, but I did find some references to old freeware lists. I seems the version I've been using is not quite the most up-to-date.
I found references to the vi, but not a downloadable copy. The references were from 1992 or so:
Chris Higgins OpenVMS Software list II. Version 8.50
Does this ring a bell? Any idea where stuff mentioned in this list might be found today? If I revive the TPU vi, I ought to get the latest one if possible.
What's the policy on submitting someone else's stuff to the freeware CD? I didn't write this, but the author included a note that it is freely distributable.
--
Robert Deininger
rdein...@mindspring.com
Charles Sebold
>> if vim is not a symbol, then it is a installed as a command and thus
>> you can't do much about it.
>
> Yes, vim is an installed program. I should know, I installed it
> myself! ;&>. I know the problem is with the program itself, because
> other programs, like the tpu editor, translate the logicals just fine.
Just to clarify: "install" doesn't just mean "the executable is on the
disk and its files are in place" in VMS lingo. If you knew this
already, then I apologize; if not, you might try "help install" to
verify what you said you know. *smiles*
--
Charles Sebold, Systems Specialist
LCMS - Office of Information Systems
*** Opinions expressed herein are not necessarily ***
*** those of the Lutheran Church - Missouri Synod ***
--
6th of Shevat, 5761
--
How to please Technologies and Micro Support:
4. When I.T. support sends you an E-Mail with high importance, delete it
at once. We're just testing.
Uncle Jeff
Charles Sebold <seb...@lcms.org> wrote:
> On 5 Shevat 5761, Uncle Jeff wrote:
>
> >> if vim is not a symbol, then it is a installed as a command and
thus
> >> you can't do much about it.
> >
> > Yes, vim is an installed program. I should know, I installed it
> > myself! ;&>. I know the problem is with the program itself, because
> > other programs, like the tpu editor, translate the logicals just
fine.
>
> Just to clarify: "install" doesn't just mean "the executable is on
the
> disk and its files are in place" in VMS lingo. If you knew this
> already, then I apologize; if not, you might try "help install" to
> verify what you said you know. *smiles*
OK, you caught me on that one. I did just mean the files are in place
on the disk. Didn't know that there was an exact translation
for 'install'. I'm more of a unix buff then a vms one, so I hope you'll
forgive the smilies ;&>.
And btw, I _will_ read the 'help install'. A closed mind is after all
an empty one!
Carl Perkins
} Charles Sebold <seb...@lcms.org> wrote:
}> On 5 Shevat 5761, Uncle Jeff wrote:
}>
}> >> if vim is not a symbol, then it is a installed as a command and
}thus
}> >> you can't do much about it.
}> >
}> > Yes, vim is an installed program. I should know, I installed it
}> > myself! ;&>. I know the problem is with the program itself, because
}> > other programs, like the tpu editor, translate the logicals just
}fine.
}>
}> Just to clarify: "install" doesn't just mean "the executable is on
}the
}> disk and its files are in place" in VMS lingo. If you knew this
}> already, then I apologize; if not, you might try "help install" to
}> verify what you said you know. *smiles*
}
}OK, you caught me on that one. I did just mean the files are in place
}on the disk. Didn't know that there was an exact translation
}for 'install'. I'm more of a unix buff then a vms one, so I hope you'll
}forgive the smilies ;&>.
}
}And btw, I _will_ read the 'help install'. A closed mind is after all
}an empty one!
}--
} ( >- THKS %^>
} /~\ Uncle Jeff (get rid of JUNK to email)
ACtually, the sense of "install" as in "installed as a command" doesn't
have anything to do with the INSTALL command either. It has more to do
with SET COMMAND...
--- Carl
Dave Weatherall
> Uncle Jeff <jeff....@federated.ca> writes...
...
> }And btw, I _will_ read the 'help install'. A closed mind is after all
> }an empty one!
> }--
> } ( >- THKS %^>
> } /~\ Uncle Jeff (get rid of JUNK to email)
>
> ACtually, the sense of "install" as in "installed as a command" doesn't
> have anything to do with the INSTALL command either. It has more to do
> with SET COMMAND...
>
> --- Carl
And then there's also 'installing' as a foreign command, as in :-
$ VIM :== $ a_disk:[a_dir]vim.exe
VMS - there's always more than one way to do it.
Cheers - Dave.