Thread: Re: [cream] Problems with Tabbed mode
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Steve H. <dig...@da...> - 2006-10-06 15:19:41
|
From: Philip Pemberton <usenet06 philpem me.uk>, Fri, Oct.06, 2006 4:47a > > Hi, > I think I've found a bug in the way Cream handles tabs on Windows (and > possibly Linux as well): > > 1. Enable Tabbed mode (Settings -> Preferences -> Tabbed Documents) > 2. Load some files, e.g. test1, test2 and test3. test3 should be > active. > 3. Drag-drop a file onto the text area. Note that test3 has been > replaced with 'dropped-file-name'. > 4. Window->'[n] test3' ([n] = a number, probably 3). Cream cycles > through all the tabs, can't find test3, so fails and drops back to > test1. > > It looks like a simple(?) case of Cream not opening a new tab when a > file is dropped on the window, which breaks the rest of the tab > handling functionality. To get the file back you can do File->New, > then "Ctrl-L :bn" until the file loads, but then you end up with > 'New File' buffers mixed in with the disc files. This is a known issue that I have procrastinated fixing forever. However, I just looked into it. Put this into cream-lib: function! Cream_tabs_focusfix() " fix when buffer externally added to session " one buffer per tab call Cream_tabpages_refresh() " goto last buffer (one just added) execute "buf " . bufnr('$') endfunction and this into cream-autocmd: autocmd FocusGained * :call Cream_tabs_focusfix() Now, dragging and dropping a filename or opening a file in Cream from an external program should maintain each file in a tab. > Also, is it possible to add a function to re-order the tabs? Vim does not currently have the capability to re-organize tabs by drag-and-drop, which would be the ideal situation. It would be possible to re-organize them by menu item, however I'm not sure what the best way to do this: o Alphabetical, by filename o Alphabetical, by path/filename o By order of being opened (buffer number) o One of the above, plus with modified first (or last) I'm not sure any of these would really be ideal in every situation, but providing multiple ways might be a bit of work. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Steve H. <dig...@da...> - 2006-10-12 00:50:43
|
From: Matt Wilkie <matt.wilkie gov yk.ca>, Wed, October 11, 2006 2:47 pm > Steve Hall wrote: > > On Tue, 2006-10-10 at 15:05 -0700, Matt Wilkie wrote: > > > > In lieu of the previous additions to cream-autocmd, use these > > > > lines: > > > umm, how does one edit this file? everytime I try and open it > > > with cream it just sits there with an hour glass indefinately. > > > > That doesn't sound right, you should be able to at least open your > > cream files, even if it is read-only due to permissions, etc. > > > > Is this file the only one, or are there others? > > it seems to be any .vim file, even an empty one. I have to use Task > Manager to "end this task" to close it down. I get the same > behaviour with just plain ol' gvim.exe. Memory usage is stable ~11mb > for gvim.exe process (just sitting there with no files open is > ~8.5mb), CPU usage is 0%. I don't have problems with other files. If > I rename the .vim file .txt I can open it no problem. > > I'm using cream 0.36, vim v7.0.17, on windows xp sp2. Have you tried upgrading your gVim with the 7.0.118(?) installer with*out* Cream available on http://cream.sf.net/download.html. It's ok to just overwrite your existing installation (it won't remove Cream), but you might want to make sure to *un-check* the option to install a context-sensitive right click menu. I seem to recall this bug being documented on the vim list at one point. -- Steve Hall [ digitect dancingpaper com ] :: Cream... something good to put in your Vim! :: http://cream.sourceforge.net |
From: Philip P. <use...@ph...> - 2006-10-06 16:48:02
|
Steve Hall wrote: > This is a known issue that I have procrastinated fixing forever. > However, I just looked into it. Put this into cream-lib: (snip patch) Hmm. It loads the new file into a tab before (to the left of) the currently-selected tab. Is it possible to make it work the other way, i.e. dropped files get new tabs on the right of the CST? > Vim does not currently have the capability to re-organize tabs by > drag-and-drop, which would be the ideal situation. It would be > possible to re-organize them by menu item, however I'm not sure what > the best way to do this: > > o Alphabetical, by filename > o Alphabetical, by path/filename > o By order of being opened (buffer number) > o One of the above, plus with modified first (or last) > > I'm not sure any of these would really be ideal in every situation, > but providing multiple ways might be a bit of work. It would be nice if you could select a tab, then right-click it and have: o Move left one tab o Move right one tab o Move to leftmost position o Move to rightmost position Alphabetical/order opened/etc. would be nice, especially with an "alphabetical sort, with this tab last" option, but I usually work with my source files in this sort of order: o main.c (leftmost) o bar.c \ o foo.c } no particular order o baz.c / o Makefile (I make a lot of makefile tweaks) In any case, Steve, thanks for all the work you've been doing on Cream. It certainly beats the alternative - digging out my Vim reference card every five seconds... "Now what was the command for 'open fold', zM or Zm? Or maybe it was zm..." Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-07 02:11:39
|
On Fri, 2006-10-06 at 17:47 +0100, Philip Pemberton wrote: > Steve Hall wrote: > > This is a known issue that I have procrastinated fixing forever. > > However, I just looked into it. Put this into cream-lib: > > (snip patch) > > Hmm. It loads the new file into a tab before (to the left of) the > currently-selected tab. Is it possible to make it work the other > way, i.e. dropped files get new tabs on the right of the CST? I just spent a number of hours on this, but unfortunately, Vim does not order tabs in any predictable way that I can see. Our use of :tab ball to keep all buffers in their own tabs randomly re-orders them sufficiently that I can't figure how to force a tab into a specific position. > It would be nice if you could select a tab, then right-click it and > have: Unfortunately, we have no control over the right-click menu. (The current one uses raw Vim commands, no Cream.) > Alphabetical/order opened/etc. would be nice, especially with an > "alphabetical sort, with this tab last" option, but I usually work > with my source files in this sort of order: > o main.c (leftmost) > o bar.c \ > o foo.c } no particular order > o baz.c / > o Makefile (I make a lot of makefile tweaks) That's what I do, too. The structure is logical, but not easily discoverable by a script. ("Main" can be called all sorts of things: index.html, index.php, cream-lib, css.php, lib.sh, etc.) > In any case, Steve, thanks for all the work you've been doing on > Cream. It certainly beats the alternative - digging out my Vim > reference card every five seconds... > "Now what was the command for 'open fold', zM or Zm? Or maybe it was > zm..." Thanks, I sometimes think that Cream is simply the usable manifestation of Vim's help. :) -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Philip P. <use...@ph...> - 2006-10-07 06:48:30
|
Steve Hall wrote: > I just spent a number of hours on this, but unfortunately, Vim does > not order tabs in any predictable way that I can see. Our use of > :tab ball to keep all buffers in their own tabs randomly re-orders > them sufficiently that I can't figure how to force a tab into a > specific position. For me, if you drop a file onto the window, it always seems to load before the tab that was open before you dropped the file... To put it another way: 1. Tabs: myfile, foo, bar [myfile active] 2. Drop 'foobar' 3. Tabs: foobar, myfile, foo, bar d > That's what I do, too. The structure is logical, but not easily > discoverable by a script. ("Main" can be called all sorts of things: > index.html, index.php, cream-lib, css.php, lib.sh, etc.) Nothing says you couldn't do "Arrange tabs alphabetically with Makefile last", then select the main()-containing file and do "Move this tab to the far left". <http://vimdoc.sourceforge.net/htmldoc/tabpage.html> explains how you can move tabs; this command moves the tab to the far left ('front'): :tabm 0 and this one to the far right ('back'): :tabm I'm not sure how you'd go about moving a tab left or right by one tab though. I suppose you'd have to find out where the tab is now, keep a count of that, subtract one, then use it as the parameter for tabm. So something like this: let newtab = bufnr("%")-2 (move left one) would tell you what to pass to tabm if you wanted to move the tab left, (and just 'bufnr("%")' on its own should give you the 'move right' offset), but I can't figure out how you'd pass that onto tabm. What I really need to do is learn how vim's internal scripting language works.. Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Philip P. <use...@ph...> - 2006-10-07 07:01:02
|
And once again Google finds something in the Vim tips database literally minutes after I posted my message... D'oh! Moving tabs left or right is explained in <http://www.vim.org/tips/tip.php?tip_id=1233>. Basically for a circular move with Alt-<comma> and Alt-<period>, you use these commands: nn <silent> <M-.> :if tabpagenr() == tabpagenr("$")\|tabm 0\|el\|exe "tabm ".tabpagenr()\|en<CR> nn <silent> <M-,> :if tabpagenr() == 1\|exe "tabm ".tabpagenr("$")\|el\|exe "tabm ".(tabpagenr()-2)\|en<CR> And for a non-circular move (i.e. Alt-. at the leftmost pos'n does nothing, vs moving to the far right for a circular move): noremap <silent> <M-Left> :exe "silent! tabmove " . (tabpagenr() - 2)<CR> noremap <silent> <M-Right> :exe "silent! tabmove " . tabpagenr()<CR> So have a 'tabm 0' and a 'tabm' command on the menu (maybe a separate Tabs menu, or Window->Tabs->... and (possibly) a shortcut key), and you can have the tabs in pretty much any order you like. 'arrange alpha with makefile last' and such would be nice, but optional. My previous comment still stands, though - learning how to write scripts for vim could be quite useful.. Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-07 12:31:57
|
On Sat, 2006-10-07 at 07:48 +0100, Philip Pemberton wrote: > Steve Hall wrote: > > I just spent a number of hours on this, but unfortunately, Vim > > does not order tabs in any predictable way that I can see. Our use > > of :tab ball to keep all buffers in their own tabs randomly > > re-orders them sufficiently that I can't figure how to force a tab > > into a specific position. > > For me, if you drop a file onto the window, it always seems to load > before the tab that was open before you dropped the file... To put > it another way: > 1. Tabs: myfile, foo, bar [myfile active] > 2. Drop 'foobar' > 3. Tabs: foobar, myfile, foo, bar Ah, I hadn't made the connection. That means you just have to change the previous mail's function with this one: function! Cream_tabs_focusgained() " 7.0+ only if v:version < 700 return endif if !exists("g:CREAM_FOCUS_BUFNR") return endif " quit if no new buffer (old and new the same) if g:CREAM_FOCUS_BUFNR == bufnr("%") return endif " one buffer per tab call Cream_tabpages_refresh() " put this new tab after the previous current tab execute "tabmove " . tabpagenr() endfunction > > That's what I do, too. The structure is logical, but not easily > > discoverable by a script. ("Main" can be called all sorts of > > things: index.html, index.php, cream-lib, css.php, lib.sh, etc.) > > Nothing says you couldn't do "Arrange tabs alphabetically with > Makefile last", then select the main()-containing file and do "Move > this tab to the far left". The definition of "main()-containing file" is the hard part. > I'm not sure how you'd go about moving a tab left or right by one > tab though. I suppose you'd have to find out where the tab is now, > keep a count of that, subtract one, then use it as the parameter for > tabm. This is what I just solved above. Using execute "tabmove " . tabpagenr() moves the current tab one place to the right. > What I really need to do is learn how vim's internal scripting > language works.. You're almost there! The two most useful documents are :help options.txt and :help eval.txt. Everything else is supplemental, especially when you can use Cream's Alt+F1 to search and Ctrl+F1 to go to a specific help topic. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Philip P. <use...@ph...> - 2006-10-08 21:01:28
|
Steve Hall wrote: > Ah, I hadn't made the connection. That means you just have to change > the previous mail's function with this one: [snip code] That did it! Thanks! > The definition of "main()-containing file" is the hard part. Just get the user to select the 'main()-containing file' and hit "Move to far left"... > This is what I just solved above. Using > > execute "tabmove " . tabpagenr() > > moves the current tab one place to the right. Heh. You didn't see my other post (with the link to the Vim tips database) then... > You're almost there! The two most useful documents are :help > options.txt and :help eval.txt. Everything else is supplemental, > especially when you can use Cream's Alt+F1 to search and Ctrl+F1 to go > to a specific help topic. I'll have a read through those then - thanks. I'll also have a look through the helpfiles and see about creating an extra 'Tabs' menu somewhere. Maybe I can implement the move-left/move-right stuff myself, and save you a job :) Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-08 23:06:22
|
On Sun, 2006-10-08 at 22:01 +0100, Philip Pemberton wrote: > Steve Hall wrote: > > > The definition of "main()-containing file" is the hard part. > > Just get the user to select the 'main()-containing file' and hit > "Move to far left"... This makes sense as a menu item. > > This is what I just solved above. Using > > > > execute "tabmove " . tabpagenr() > > > > moves the current tab one place to the right. > > Heh. You didn't see my other post (with the link to the Vim tips > database) then... I saw it after I replied, good answer! :) > I'll also have a look through the helpfiles and see about creating > an extra 'Tabs' menu somewhere. Maybe I can implement the > move-left/move-right stuff myself, and save you a job :) Sounds good to me! Make "Tabs" a submenu of Window. It should probably have "t" as the accelorator after first removing it from the existing item to create a new instance. And in case you haven't done it yet, try putting let g:cream_devel = 1 in your cream-user.vim. It will give you the Cream Developer menu and make available everything in cream-devel and cream-playpen. (I tend to put test routines in the latter until they're complete.) -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Steve H. <dig...@da...> - 2006-10-07 02:16:16
|
On Fri, 2006-10-06 at 21:38 +0100, Philip Pemberton wrote: > Steve, > There seems to be a bit of an issue with the patch: > 1. Open Cream by right-clicking a file and selecting "Open in > Cream/Vim" > 2. Select an Explorer / directory display window with Alt-tab, or > just give it focus by clicking the title-bar > 3. Drop a file onto Cream. Cream takes focus, then opens the file in > a new tab. > 4. Alt-tab away from Cream, then alt-tab back. Sometimes when you do > this, some tabs will double up and others will disappear. > Alt-tabbing back and forth a few times sometimes gets them to > reappear, sometimes not. Yes, the problem is that the (overly-simplistic) "patch" did not verify whether a new buffer had been added or not. I've worked out a way to fix this though: In lieu of the previous additions to cream-autocmd, use these lines: " fix tab mis-count issue autocmd FocusLost * call Cream_tabs_focuslost() autocmd FocusGained * call Cream_tabs_focusgained() and in lieu of the previous cream-lib-win-tab-buf additions, use these: function! Cream_tabs_focusgained() " fix when buffer externally added to session " 7.0+ only if v:version < 700 return endif if !exists("g:CREAM_FOCUS_BUFNR") return endif " quit if no new buffer (old and new the same) if g:CREAM_FOCUS_BUFNR == bufnr("%") return endif " one buffer per tab call Cream_tabpages_refresh() " attempt to put this new tab after the previous current tab... endfunction function! Cream_tabs_focuslost() " remember current buffer when focus lost " 7.0+ only if v:version < 700 return endif let g:CREAM_FOCUS_BUFNR = bufnr("%") endfunction -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Matt W. <mat...@go...> - 2006-10-11 18:47:16
|
Steve Hall wrote: > On Tue, 2006-10-10 at 15:05 -0700, Matt Wilkie wrote: >>> In lieu of the previous additions to cream-autocmd, use these >>> lines: >> umm, how does one edit this file? everytime I try and open it with >> cream it just sits there with an hour glass indefinately. > > That doesn't sound right, you should be able to at least open your > cream files, even if it is read-only due to permissions, etc. > > Is this file the only one, or are there others? it seems to be any .vim file, even an empty one. I have to use Task Manager to "end this task" to close it down. I get the same behaviour with just plain ol' gvim.exe. Memory usage is stable ~11mb for gvim.exe process (just sitting there with no files open is ~8.5mb), CPU usage is 0%. I don't have problems with other files. If I rename the .vim file .txt I can open it no problem. I'm using cream 0.36, vim v7.0.17, on windows xp sp2. -- matt wilkie -------------------------------------------- Geographic Information, Information Management and Technology, Yukon Department of Environment 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9 867-667-8133 Tel * 867-393-7003 Fax http://environmentyukon.gov.yk.ca/geomatics/ -------------------------------------------- |
From: Philip P. <use...@ph...> - 2006-10-06 20:38:19
|
Steve, There seems to be a bit of an issue with the patch: 1. Open Cream by right-clicking a file and selecting "Open in Cream/Vim" 2. Select an Explorer / directory display window with Alt-tab, or just give it focus by clicking the title-bar 3. Drop a file onto Cream. Cream takes focus, then opens the file in a new tab. 4. Alt-tab away from Cream, then alt-tab back. Sometimes when you do this, some tabs will double up and others will disappear. Alt-tabbing back and forth a few times sometimes gets them to reappear, sometimes not. Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: David H. <met...@fa...> - 2006-10-06 21:02:44
|
That one is conceivably an issue with Vim... -d Philip Pemberton wrote: > Steve, > There seems to be a bit of an issue with the patch: > 1. Open Cream by right-clicking a file and selecting "Open in Cream/Vim" > 2. Select an Explorer / directory display window with Alt-tab, or just give it > focus by clicking the title-bar > 3. Drop a file onto Cream. Cream takes focus, then opens the file in a new tab. > 4. Alt-tab away from Cream, then alt-tab back. Sometimes when you do this, > some tabs will double up and others will disappear. Alt-tabbing back and forth > a few times sometimes gets them to reappear, sometimes not. > > Thanks. |
From: Matt W. <mat...@go...> - 2006-10-10 22:05:13
|
> In lieu of the previous additions to cream-autocmd, use these lines: umm, how does one edit this file? everytime I try and open it with cream it just sits there with an hour glass indefinately. cheera, -- matt wilkie -------------------------------------------- Geographic Information, Information Management and Technology, Yukon Department of Environment 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9 867-667-8133 Tel * 867-393-7003 Fax http://environmentyukon.gov.yk.ca/geomatics/ -------------------------------------------- |
From: Steve H. <dig...@da...> - 2006-10-11 03:34:38
|
On Tue, 2006-10-10 at 15:05 -0700, Matt Wilkie wrote: > > In lieu of the previous additions to cream-autocmd, use these > > lines: > > umm, how does one edit this file? everytime I try and open it with > cream it just sits there with an hour glass indefinately. That doesn't sound right, you should be able to at least open your cream files, even if it is read-only due to permissions, etc. Is this file the only one, or are there others? -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Philip P. <use...@ph...> - 2006-10-12 22:50:11
|
Steve Hall wrote: >>> The definition of "main()-containing file" is the hard part. >> Just get the user to select the 'main()-containing file' and hit >> "Move to far left"... > > This makes sense as a menu item. My patch to cream-menu-window.vim: " add tab handling functions to the menu anoremenu <silent> 80.590 &Window.-SEP450- <Nul> anoremenu <silent> 80.591 &Window.&Tabs.Make\ Tab\ &First :tabmove 0<CR> anoremenu <silent> 80.591 &Window.&Tabs.Move\ Tab\ &Left :if tabpagenr() == 1\|exe "tabm ".tabpagenr("$")\|el\|exe "tabm ".(tabpagenr()-2)\|en<CR> anoremenu <silent> 80.591 &Window.&Tabs.Move\ Tab\ &Right :if tabpagenr() == tabpagenr("$")\|tabm 0\|el\|exe "tabm ".tabpagenr()\|en<CR> anoremenu <silent> 80.591 &Window.&Tabs.Make\ Tab\ Las&t :tabmove<CR> Problem is, when you click on one of those menu items, the tab bar doesn't update until you move to a different tab and back again... > And in case you haven't done it yet, try putting > > let g:cream_devel = 1 > > in your cream-user.vim. It will give you the Cream Developer menu and > make available everything in cream-devel and cream-playpen. (I tend to > put test routines in the latter until they're complete.) That doesn't seem to do anything... Oh, BTW, I found a bug in the save-as handling stuff. If you create (or load) a file, then use Save As to save it, parts of the colour scheme change (mainly text colours AFAICT). It also seems Cream doesn't close/delete the buffer (:bd) when the relevant tab is closed. I'm not sure if this is a bug or not... Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-14 16:53:32
|
On Thu, 2006-10-12 at 23:36 +0100, Philip Pemberton wrote: > Steve Hall wrote: > > > > > > Just get the user to select the 'main()-containing file' and hit > > > "Move to far left"... > > > > This makes sense as a menu item. > > My patch to cream-menu-window.vim: > > " add tab handling functions to the menu > anoremenu <silent> 80.590 &Window.-SEP450- <Nul> > anoremenu <silent> 80.591 &Window.&Tabs.Make\ Tab\ &First :tabmove 0<CR> > anoremenu <silent> 80.591 &Window.&Tabs.Move\ Tab\ &Left :if tabpagenr() == 1\|exe "tabm ".tabpagenr("$")\|el\|exe "tabm ".(tabpagenr()-2)\|en<CR> > anoremenu <silent> 80.591 &Window.&Tabs.Move\ Tab\ &Right :if tabpagenr() == tabpagenr("$")\|tabm 0\|el\|exe "tabm ".tabpagenr()\| en<CR> > anoremenu <silent> 80.591 &Window.&Tabs.Make\ Tab\ Las&t :tabmove<CR> Nice! However I'm going to reject it as a teaching device. :)) As a rule, all Cream features should be accomplished via calls to functions. This is for several reasons: 1. Vim has difficulty knowing what mode it is in from within a command or function. Everything is conditional, and the odd <Esc> or imap will fail in the wrong state. Early on, this caused me IMENSE frustration and I spent a lot of time fixing things that were only broken in certain conditions. But I eventually discovered that it is much cleaner to write normal mode functions, and use mode-specific mechanisms to enter normal mode and call them. In the occasional condition where a function needs to be called from another mode (such as with a selection) the mode is passed to the function as an argument. For example: function! MyFunction(mode) if a:mode == "i" " do insert mode stuff elseif a:mode == "v" " do visual mode stuff endif endfunction imap <silent> <C-o>:call MyFunction("i")<CR> vmap <silent> :<C-u>call MyFunction("v")<CR> 2. As Cream has developed, its developer has gotten smarter. :) Functions can be called by other functions, there's no reason to write something twice. In your example functionalites, it is very conceivable that some functionality in the future may want to re-order tabs. If these four uses are functions, it is easy to call them: call Cream_tab_move_left() Plus, you may want to attach both a keyboard mapping and a menu item to the same functionality. 3. Some day in the future, I can imagine user-definable mappings or mapping schemes. The mappings will need to be abstracted and this won't be possible if their right-hand sides (:help rhs) are command strings. It should take you five minutes to abstract these following the model (in cream-lib-win-tab-buf.vim) function! Cream_tab_move_first() tabmove 0 endfunction (in cream-menu-window.vim) imenu <silent> 80.591 &Window.&Tabs.Make\ Tab\ &First <C-o>:call Cream_tab_move_first()<CR> vmenu <silent> 80.592 &Window.&Tabs.Make\ Tab\ &First :<C-u>call Cream_tab_move_first()<CR> > Problem is, when you click on one of those menu items, the tab bar > doesn't update until you move to a different tab and back again... This could very well be caused by the mode switching problem I discussed above! > > And in case you haven't done it yet, try putting > > > > let g:cream_devel = 1 > > > > in your cream-user.vim. It will give you the Cream Developer menu > > and make available everything in cream-devel and cream-playpen. (I > > tend to put test routines in the latter until they're complete.) > > That doesn't seem to do anything... Double-whoops, that should be in your cream-conf, and be: let g:cream_dev = 1 > Oh, BTW, I found a bug in the save-as handling stuff. If you create > (or load) a file, then use Save As to save it, parts of the colour > scheme change (mainly text colours AFAICT). I'll put this on the ToDo. > It also seems Cream doesn't close/delete the buffer (:bd) when the > relevant tab is closed. I'm not sure if this is a bug or not... Are you using the right click menu? That is a known bug, these is a hard-coded Vim menu that we can't turn off or customize. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Matt W. <mat...@go...> - 2006-10-13 15:50:15
|
> Oh, BTW, I found a bug in the save-as handling stuff. If you create (or load) > a file, then use Save As to save it, parts of the colour scheme change (mainly > text colours AFAICT). I can confirm this. It's been this way since I first discovered Cream at v0.29(?). One of those little things that just didn't seem to be worth the time of documenting; so thank you for taking the time! cheers, -- matt wilkie -------------------------------------------- Geographic Information, Information Management and Technology, Yukon Department of Environment 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9 867-667-8133 Tel * 867-393-7003 Fax http://environmentyukon.gov.yk.ca/geomatics/ -------------------------------------------- |
From: Philip P. <use...@ph...> - 2006-10-13 20:37:06
|
Matt Wilkie wrote: > I can confirm this. It's been this way since I first discovered Cream at > v0.29(?). One of those little things that just didn't seem to be worth > the time of documenting; so thank you for taking the time! As a developer, these kind of comments make me cringe... I've lost count of the number of times I've fixed something, mentioned it on the project mailing list (or in the CHANGELOG), and someone's said "Oh, I saw that in 0.93 [when current version is 1.15 or so] but I didn't mention it because I didn't think it was a very serious problem." *sigh* -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-14 17:01:49
|
On Fri, 2006-10-13 at 16:34 -0700, Matt Wilkie wrote: > > As a developer, these kind of comments make me cringe... > > :) sorry 'bout that. > > I'm apprehensive about logging every irritation or discontinuity. In > some (most?) places that just gets you thrown into the crank bin and > then when you do bring up something serious it's more likely to be > ignored. Or at least that's been my personal experience. That's been my observation on other projects (like Vim!) as well, so I try to only file the ones that are critical (to me). Relative to Cream, I try to log every known or confirmed bug, but with just an hour or two a week to devote to Cream at the moment, you'll notice the ToDo list is getting quite long (760 lines). Over the three areas of development efforts: 1. Bug fixing 2. Feature additions 3. Personal itch scratching there is definitely a need to grow the development team! -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Philip P. <use...@ph...> - 2006-10-13 20:53:42
|
Matt Wilkie wrote: > it seems to be any .vim file, even an empty one. I have to use Task > Manager to "end this task" to close it down. I get the same behaviour > with just plain ol' gvim.exe. Memory usage is stable ~11mb for gvim.exe > process (just sitting there with no files open is ~8.5mb), CPU usage is > 0%. I don't have problems with other files. If I rename the .vim file > .txt I can open it no problem. I wonder if the syntax highlighter file for .vim files is corrupted... -- Phil. | (\_/) This is Bunny. Copy and paste Bunny use...@ph... | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | (")_(") world domination. If mail bounces, replace "06" with the last two digits of the current year. |
From: Steve H. <dig...@da...> - 2006-10-14 16:54:57
|
On Fri, 2006-10-13 at 21:53 +0100, Philip Pemberton wrote: > Matt Wilkie wrote: > > it seems to be any .vim file, even an empty one. I have to use > > Task Manager to "end this task" to close it down. I get the same > > behaviour with just plain ol' gvim.exe. Memory usage is stable > > ~11mb for gvim.exe process (just sitting there with no files open > > is ~8.5mb), CPU usage is 0%. I don't have problems with other > > files. If I rename the .vim file .txt I can open it no problem. > > I wonder if the syntax highlighter file for .vim files is > corrupted... That's what I'm wondering, but it will be a few days before I can get back to a Windows machine to test. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Steve H. <dig...@da...> - 2006-10-19 00:37:37
|
On Fri, 2006-10-13 at 21:53 +0100, Philip Pemberton wrote: > Matt Wilkie wrote: > > it seems to be any .vim file, even an empty one. I have to use > > Task Manager to "end this task" to close it down. I get the same > > behaviour with just plain ol' gvim.exe. Memory usage is stable > > ~11mb for gvim.exe process (just sitting there with no files open > > is ~8.5mb), CPU usage is 0%. I don't have problems with other > > files. If I rename the .vim file .txt I can open it no problem. > > I wonder if the syntax highlighter file for .vim files is > corrupted... I am unable to re-produce this, on either Windows or GNU/Linux. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Matt W. <mat...@go...> - 2006-10-13 23:34:48
|
> As a developer, these kind of comments make me cringe... :) sorry 'bout that. I'm apprehensive about logging every irritation or discontinuity. In some (most?) places that just gets you thrown into the crank bin and then when you do bring up something serious it's more likely to be ignored. Or at least that's been my personal experience. -- matt wilkie -------------------------------------------- Geographic Information, Information Management and Technology, Yukon Department of Environment 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9 867-667-8133 Tel * 867-393-7003 Fax http://environmentyukon.gov.yk.ca/geomatics/ -------------------------------------------- |
From: Steve H. <dig...@da...> - 2006-10-14 17:27:44
|
On Fri, 2006-10-13 at 16:34 -0700, Matt Wilkie wrote: > > I'm apprehensive about logging every irritation or discontinuity. In > some (most?) places that just gets you thrown into the crank bin and > then when you do bring up something serious it's more likely to be > ignored. Or at least that's been my personal experience. That's been my observation on other projects (like Vim) as well, so I try to only file the ones that are critical (to me). Relative to Cream, I try to log every known or confirmed bug, but you'll notice the ToDo list is getting quite long (760 lines). Over the three areas of development efforts: 1. Bug fixing 2. Feature additions 3. Personal itch scratching there is definitely a need to grow the development team! -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |