From: Ivailo Stoyanov, Feb 10, 2004 3:18 AM
> > >
> > > 1) CREAM environment variable not set --> ``ERROR! $CREAM
> > > location not discovered! Cream not loaded.''
> > This one troubles me, Cream shouldn't have any problem setting
> > path when using the default installation. I know we're working on
> > a bug when your $CREAM path is set, but I'd like to figure out why
> > it fails when it isn't.
> > Do you have an environmental variable %VIMINIT% set? How about
> > %VIM%? What is the output of ":echo $VIM" and ":echo $VIMRUNTIME"
> > from within Vim?
> > (Do these requests make sense? I don't remember if you said you've
> > used Vim before--if the command line entries, beginning with ":",
> > don't make sense, let me know.)
> I am an absolute gVim newbie -- I ``discovered'' Vim about two weeks
> ago, and if I hadn't found the Cream shortly after that, I think I
> couldn't get a lot out of this slightly complicated editor;).
> So I haven't messed with environment variables at all neither after
> I had firstly installed the official Vim (+ Cream 0.27 manually),
> nor after I had gVim 6.2.170 + Cream 0.27 installed. Only after I
> experienced the noted difficulties, I read the FAQ and tried to
> solve the problem by setting the CREAM variable, but nothing more.
> I have read meanwhile about the ``:'' commands, but I had not found
> a way to use them under Cream (perhaps I have to read some more
If you press Ctrl+L you pop into Vim's normal mode and your cursor
should turn red. This is the "normal mode" typical Vim users start in
and usually work from. Then, from normal mode, you type ":" to pop
down to the command line. You can enter all sorts of command here.
Generally, when someone provides Vim help, they just give it as a
command such as ":help startup" or ":help $VIM".
Cream has an add-on Tools=>Add-ons=>Cream Config Info that will
generate a report with all your environmental settings. Please save
this as a file and mail it to me off-list (it's rather large). Maybe I
can figure out what is happening.
> > > 6) The mentioned right-click anomaly disappeared when I
> > > restarted the machine.
> > Good, hopefully this is resolved.
> BUT I noticed that on right-click in the buffer-windows the
> context-menu has the first row BLANK (i.e. from top to bottom: BLANK
> | Undo Paste Select all), so there seems to exist a right-click
> | bug(?) after all:(
No, this is a work-around for a problem that occurs in Linux GNOME.
(When first focusing the window and picking right click, the first
entry would automatically be entered and the menu closed.) Perhaps I
should have made that conditional so it doesn't look like a bug on
Steve Hall [ digitect@... ]
Cream... the Vim text editor in sheep's clothing!