Thread: Re: gvim 6.2.225 + cream 0.28: multiple user problems
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Steve H. <dig...@mi...> - 2004-02-06 14:41:43
Attachments:
cream-menu-toolbar.vim
|
From: Ivailo Stoyanov, Feb 6, 2004 5:33 AM > > Dear ListMembers, > > Today I downloaded the brand-new version of gvim+cream and after > installation I experienced following multiuser troubles: > > Install as ``Administrator'' and run --> everything is O.K. > > Log-in as ``user'' and run --> ``ERROR! Can't find loader. Cream not > loaded.'' > > After reading through the FAQ, I set the ``CREAM'' environmental > variable for ``user'' e.g. ''CREAM=C:\program Files\vim\cream\'', In DOS, that should be: set CREAM=C:\PROGRA~1\VIM\CREAM\ Be careful about using paths with spaces as Windows does strange things with them when quoted. Also verify trailing backslash. > and at a consecutive run I got the following error: > > ``Error detected while processing C:/Program > Files/vim/cream/cream-menu-toolbar.vim: line 46: > E121: Undefined variable: creamfix A bug in the code. Please test the attached cream-menu-toolbar.vim, replacing your file by the same name. Fixed? -- Steve Hall [ dig...@mi... ] Cream... the Vim text editor in sheep's clothing! http://cream.sourceforge.net |
From: Steve H. <dig...@mi...> - 2004-02-10 15:53:51
|
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 > documentation?). 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 Windows. -- Steve Hall [ dig...@mi... ] Cream... the Vim text editor in sheep's clothing! http://cream.sourceforge.net |
From: Steve H. <dig...@mi...> - 2004-02-10 16:03:13
Attachments:
cream-menu-toolbar.vim
|
From: Ivailo Stoyanov, Feb 10, 2004 4:06 AM > > > Please make sure your new line 48 is blank, and doesn't include > > the line 48 from the unpatched version above. There should be no > > references to the variable "creamfix" remaining. > > > > > 5) CREAM variable set to ``C:\Progra~1\vim\cream\'' + new lines > > > 41-48 --> the same result as described under 4). > > > > Should be ok if line 48 is blank. > > I have deleted the whole contents of line 48 > ``let myruntimepath = creamfix . "," . &runtimepath'' > in cream-menu-toolbar.vim... Woops, wrong line. Please try the attached file, replacing your current file with the same name. > PS. By the way, changing the trailing "/" to "\" in $CREAM does not > make any difference. Does it with this new file? -- Steve Hall [ dig...@mi... ] Cream... the Vim text editor in sheep's clothing! http://cream.sourceforge.net |
From: Ivailo S. <ist...@fr...> - 2004-02-10 17:04:13
|
Dear Steve, > Woops, wrong line. Please try the attached file, replacing your > current file with the same name. Equipped with the new ``cream-menu-toolbar.vim'' everything works fine now!!! > > PS. By the way, changing the trailing "/" to "\" in $CREAM does not > > make any difference. Although now this shouldn't matter, I can confirm that this remains true -- i.e. gVim & Cream start smoothly regardless of the type of trailing slash in the environmental variable;) Thank you for the help! All the best, Ivailo |
From: Steve H. <dig...@mi...> - 2004-02-07 03:47:26
|
From: Ivailo Stoyanov, Fri Feb 6 2004 > > I just mailed my previous notice and realised, that the problem > seems to be fixed when starting gVim from its shortcut, but the > toolbar REMAINS empty when opening a file through the right-click > menu item ``edit with Gvim''!!! > > However, the corresponding tooltips appear, and the functionality is > not otherwise changed when pressing in the empty squares on the > toolbar... Let's back up a second and let me ask a few questions: o Will Cream not operate correctly if you clear your DOS environment variable %CREAM%? Is it all of Cream or just the toolbar icons? o What happens if you change the backslashes ("\") in the %CREAM% var's path to forward slashes ("/")? If this second method fixes it, you may have discovered a bug I just noticed in the same file we already updated. With your path back in the "correct" (backslash) form (with trailing!), please try substituting the following lines in cream-menu-toolbar.vim: 41:" remove trailing slash from $CREAM 42:if strpart($CREAM, strlen($CREAM) - 1) == "/" 43: let creamfix = strpart($CREAM, 0, strlen($CREAM) - 1) 44:else 45: let creamfix = $CREAM 46:endif 47:" concatenate 48:let myruntimepath = creamfix . "," . &runtimepath with these: 41:" remove trailing slash from $CREAM 42:if matchstr($CREAM, '.$') == '/' 43:\|| matchstr($CREAM, '.$') == '\' 44: let myruntimepath = matchstr($CREAM, '^.*\(.$\)\@=') . "," . &runtimepath 45:else 46: let myruntimepath = $CREAM . "," . &runtimepath 47:endif 48: Removing the line numbers above, of course. (And beware of linewraps inserted by our mailer!) Fixed? -- Steve Hall [ dig...@mi... ] Cream... sheep clothing for the Vim text editor! http://cream.sourceforge.net |
From: Ivailo S. <ist...@fr...> - 2004-02-09 08:21:03
|
Dear Steve, please accept my apologies for my (presumably) unclear expression, but English is not my native language. Anyway, I have experimented with all the new information I've got, so here I sum up everything again: 1) CREAM environment variable not set --> ``ERROR! $CREAM location not discovered! Cream not loaded.'' 2) CREAM variable set to ``C:\Progra~1\vim\cream\'' --> Cream loaded, BUT the toolbar icons do not appear. 3) CREAM variable set to ``C:\Progra~1\vim\cream/'' + modified cream-menu-toolbar.vim (the one you sent me as attachment) --> everything works OK. > 41:" remove trailing slash from $CREAM > 42:if strpart($CREAM, strlen($CREAM) - 1) == "/" > 43: let creamfix = strpart($CREAM, 0, strlen($CREAM) - 1) > 44:else > 45: let creamfix = $CREAM > 46:endif > 47:" concatenate > 48:let myruntimepath = creamfix . "," . &runtimepath > > with these: > > 41:" remove trailing slash from $CREAM > 42:if matchstr($CREAM, '.$') == '/' > 43:\|| matchstr($CREAM, '.$') == '\' > 44: let myruntimepath = matchstr($CREAM, '^.*\(.$\)\@=') . "," . > &runtimepath > 45:else > 46: let myruntimepath = $CREAM . "," . &runtimepath > 47:endif > 48: 4) CREAM variable set to ``C:\Progra~1\vim\cream/'' + modified lines 41-48 as suggested --> ``Error detected while C:/Program Files/vim/cream/cream-menu-toolbar.vim line 49: E121: Undefined variable: creamfix E15: Invalid expression: creamfix . "," . &runtimepath'', BUT afterwards Cream starts as expected. 5) CREAM variable set to ``C:\Progra~1\vim\cream\'' + new lines 41-48 --> the same result as described under 4). 6) The mentioned right-click anomaly disappeared when I restarted the machine. Hope that this is now much more clearer;) For the moment I successfully use configuration #3) without any further problems. Thank you for providing this marvelous piece of software to the community!!! All the best, Ivailo |