Hello,
I'm not sure if this problem is
inherently vim's, solaris's, windows,
twm, or vnc.
I use TightVNC 1.2.2 to connect to twm
running on solaris 8. I've got a twm
menu item set to call a script
~/bin/gvim, which consists of the
following lines:
#!/bin/SomeShell
/Directory/of/gvim/executable/gvim \
-N \
-u /home/Me/.vimrc \
-U /home/Me/.gvimrc $*
This script works fine from the command
line. If I invoke it using twm menus,
it hangs the twm window manager if the
display is pseudocolor (it is a VNC
desktop). Twm doesn't respond at all
until I kill the gvim related processes.
I don't have this problem if the desktop
is true-color.
I've tried with csh, tcsh, and bash in
place of SomeShell above. Note that
twm shells out with "sh -c", but I can
pass "csh -c gvim" to the "sh -c"
command. (It doesn't have to be csh,
can be any other shell). Due to my path
arrangement, gvim resolves to the 3-line
script above, which in turn invokes the
gvim binary executable.
No processes are taking up any CPU when
it hangs.
I compared the command-line behaviours
on pseudocolor and true color displays.
The only difference is that the pseudo-
color display generates the error
Vim: (ec1) Cannot allocate colormap
entry, some colors may be incorrect
The colormap problem might be alleviated
by shutting down other applications (and
restarting them after gvim), but that's
a pain. It's faster just to use the
command line to start gvim to avoid the
hanging. But I'd like to get it working
with twm menus, without changing any of
the colors that took so long to
finalize.
I thought vim might be hanging because
it has no place to print its error
message when invoked from twm. So I
redirected stderr and stdout to
/dev/null. No luck.
Does anyone have any ideas on this?
Fred
--
Fred Ma, [EMAIL PROTECTED]
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
