Hey,
I’m using vim 6.1 on QNX4 and I’m having troubles editing files across a
QNX network, i.e. //1/etc/hosts. The problem is not when it opens, which
happens just find, but when I go to write the file out. It seems to
think the pathname is “1/etc/hosts” instead of “//1/etc/hosts”. The
weird thing is that it doesn’t happen with all our QNX4 machines even
though they have the same version, .vimrc files and .profile. Does
anyone know how to fix this? I’ve tried elvis on the same machines that
have problems with vim and they can open and write a file across the
network find if that is helpful to know.
Eric
Eric Norton <enorton_nospam@nospam_fct.ca> wrote:
Hey,
I’m using vim 6.1 on QNX4 and I’m having troubles editing files across a
QNX network, i.e. //1/etc/hosts. The problem is not when it opens, which
happens just find, but when I go to write the file out. It seems to
think the pathname is “1/etc/hosts” instead of “//1/etc/hosts”. The
weird thing is that it doesn’t happen with all our QNX4 machines even
though they have the same version, .vimrc files and .profile. Does
anyone know how to fix this? I’ve tried elvis on the same machines that
have problems with vim and they can open and write a file across the
network find if that is helpful to know.
Can you write the file out with an explicit:
:w //1/etc/hosts
It sounds like the port of vim is doing something wrong/broken with
the // in the filename. The QNX4 use of // as something special at
the start of a pathname is non-Unixy, though allowed by POSIX, and
so may confuse ported code if it wasn’t ported quite right.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
“Eric Norton” <enorton_nospam@nospam_fct.ca> wrote in message
news:crk6a2$nk9$1@inn.qnx.com…
Hey,
I’m using vim 6.1 on QNX4 and I’m having troubles editing files across a
QNX network, i.e. //1/etc/hosts. The problem is not when it opens, which
happens just find, but when I go to write the file out. It seems to think
the pathname is “1/etc/hosts” instead of “//1/etc/hosts”. The weird thing
is that it doesn’t happen with all our QNX4 machines even though they have
the same version, .vimrc files and .profile. Does anyone know how to fix
this? I’ve tried elvis on the same machines that have problems with vim
and they can open and write a file across the network find if that is
helpful to know.
From memory when I ported vim 6.? to QNX4 I had to make a change to support
// don’t remember where it was though.
Eric
Eric Norton <enorton_nospam@nospam_fct.ca> wrote:
Hey,
I’m using vim 6.1 on QNX4 and I’m having troubles editing files across a
QNX network, i.e. //1/etc/hosts. The problem is not when it opens, which
happens just find, but when I go to write the file out. It seems to
think the pathname is “1/etc/hosts” instead of “//1/etc/hosts”. The
weird thing is that it doesn’t happen with all our QNX4 machines even
though they have the same version, .vimrc files and .profile. Does
anyone know how to fix this? I’ve tried elvis on the same machines that
have problems with vim and they can open and write a file across the
network find if that is helpful to know.
Eric
I suggest you try Mario’s vim 6.2 port for QNX 4:
http://sourceforge.net/projects/openqnx
David Gibbs wrote:
Eric Norton <enorton_nospam@nospam_fct.ca> wrote:
Hey,
I’m using vim 6.1 on QNX4 and I’m having troubles editing files across a
QNX network, i.e. //1/etc/hosts. The problem is not when it opens, which
happens just find, but when I go to write the file out. It seems to
think the pathname is “1/etc/hosts” instead of “//1/etc/hosts”. The
weird thing is that it doesn’t happen with all our QNX4 machines even
though they have the same version, .vimrc files and .profile. Does
anyone know how to fix this? I’ve tried elvis on the same machines that
have problems with vim and they can open and write a file across the
network find if that is helpful to know.
Can you write the file out with an explicit:
:w //1/etc/hosts
It sounds like the port of vim is doing something wrong/broken with
the // in the filename. The QNX4 use of // as something special at
the start of a pathname is non-Unixy, though allowed by POSIX, and
so may confuse ported code if it wasn’t ported quite right.
-David
I tried that as well and it reported that it couldn’t write to “1/etc/hosts”
Eric