cream-general Mailing List for Cream (for Vim) (Page 2)
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(7) |
Nov
(17) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(7) |
Feb
|
Mar
(34) |
Apr
(34) |
May
(3) |
Jun
(9) |
Jul
(29) |
Aug
(22) |
Sep
(36) |
Oct
(43) |
Nov
(15) |
Dec
(3) |
2004 |
Jan
(13) |
Feb
(25) |
Mar
(72) |
Apr
(45) |
May
(47) |
Jun
(36) |
Jul
(25) |
Aug
(33) |
Sep
(22) |
Oct
(68) |
Nov
(58) |
Dec
(30) |
2005 |
Jan
(46) |
Feb
(46) |
Mar
(34) |
Apr
(65) |
May
(24) |
Jun
(13) |
Jul
(12) |
Aug
(21) |
Sep
(19) |
Oct
(12) |
Nov
(25) |
Dec
(65) |
2006 |
Jan
(23) |
Feb
(15) |
Mar
(36) |
Apr
(47) |
May
(47) |
Jun
(51) |
Jul
(23) |
Aug
(14) |
Sep
(23) |
Oct
(47) |
Nov
(33) |
Dec
(10) |
2007 |
Jan
(4) |
Feb
(6) |
Mar
(2) |
Apr
(10) |
May
(27) |
Jun
(8) |
Jul
(12) |
Aug
(52) |
Sep
(17) |
Oct
(7) |
Nov
(3) |
Dec
(42) |
2008 |
Jan
(21) |
Feb
(22) |
Mar
(7) |
Apr
(6) |
May
(13) |
Jun
(5) |
Jul
(4) |
Aug
(5) |
Sep
|
Oct
|
Nov
(22) |
Dec
(4) |
2009 |
Jan
(2) |
Feb
(16) |
Mar
(5) |
Apr
(1) |
May
(6) |
Jun
(3) |
Jul
(6) |
Aug
(8) |
Sep
|
Oct
(36) |
Nov
(4) |
Dec
(4) |
2010 |
Jan
(3) |
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
|
2011 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
(7) |
May
(14) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2013 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(7) |
Oct
(5) |
Nov
|
Dec
(2) |
2014 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steve H. <dig...@da...> - 2013-10-27 20:07:28
|
On Sun, Oct 27, 2013 at 2:03 AM, Dmitry Frank <dim...@gm...> wrote: > > > > > > Could you please build Vim 7.4 with +ruby and +python again? Or, > > > why have you decided to exclude these features? [...] For anyone following this thread, I have just posted a Windows installer updated to 7.4.52: http://sourceforge.net/projects/cream/files/Vim/ The release notes are there, but I'll point out Perl, Ruby, and TCL are all still broken in the Cygwin build process of a stand-alone (non-Cygwin dependent) gVim. Still no updates on the Cream side... yet. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim [ http://cream.sourceforge.net ] |
From: Dmitry F. <dim...@gm...> - 2013-10-27 06:03:34
|
I'm using Python2. I see that Vim binary has +python3/dyn, but -python and -ruby. Please note that another Vim 7.4 binary is built successfully with +python and +ruby : http://tuxproject.de.nyud.net/projects/vim/<http://goo.gl/BzdkjM>(current version is 7.4.51 there) 2013/10/27 Steve Hall <dig...@da...> > On Sat, Oct 26, 2013 at 2:52 PM, Dmitry Frank <dim...@gm...> > wrote: > > > > I just have noticed that Vim 7.4.x built for Windows are built with > > -ruby and -python . This is pretty disappointed for me, I have to > > switch back to 7.3.x, since it is built with +ruby and +python. > > > > Could you please build Vim 7.4 with +ruby and +python again? Or, why > > have you decided to exclude these features? > > What version of Python are you trying to use? I'm working today on > getting both 2 and 3 included instead of just the first. We'll see. > > I'm disappointed about the Ruby, too, but Vim's build system has been > long broken with these features. I think there was a recent patch, so > maybe it is finally fixed. I'll include features as soon as Vim's > build works with them. > > -- > Steve Hall [ digitect dancingpaper com ] > :: Cream for Vim http://cream.sourceforge.net > |
From: Steve H. <dig...@da...> - 2013-10-26 23:04:15
|
On Sat, Oct 26, 2013 at 2:52 PM, Dmitry Frank <dim...@gm...> wrote: > > I just have noticed that Vim 7.4.x built for Windows are built with > -ruby and -python . This is pretty disappointed for me, I have to > switch back to 7.3.x, since it is built with +ruby and +python. > > Could you please build Vim 7.4 with +ruby and +python again? Or, why > have you decided to exclude these features? What version of Python are you trying to use? I'm working today on getting both 2 and 3 included instead of just the first. We'll see. I'm disappointed about the Ruby, too, but Vim's build system has been long broken with these features. I think there was a recent patch, so maybe it is finally fixed. I'll include features as soon as Vim's build works with them. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim http://cream.sourceforge.net |
From: Dmitry F. <dim...@gm...> - 2013-10-26 18:52:37
|
Hello. I just have noticed that Vim 7.4.x built for Windows are built with -ruby and -python . This is pretty disappointed for me, I have to switch back to 7.3.x, since it is built with +ruby and +python. Could you please build Vim 7.4 with +ruby and +python again? Or, why have you decided to exclude these features? Thanks. -- Dmitry |
From: umberto b. <ve...@gm...> - 2013-09-17 20:47:32
|
On Mon, Sep 16, 2013 at 5:38 AM, Steve Hall <dig...@da...>wrote: > The intended behavior should be the word behind/preceeding. With Ctrl, > the Backspace key should simply take a bigger gulp. I'll look into > this. > One further bug report detail: it works correctly (deletes preceeding word) only if the cursor is at the end of the line. If any characters follow the cursor (white space included) it behaves incorrectly. > > I'm pleased to say that over the last few days I've gotten back into > some new programming for Cream for the first time in years. I'm > getting a new build system up and running and hope to release new > Window Vim binaries and a new Cream version soon! > Thanks for the good work. Looking forward to it. Truly vim is a too stringent for me to use without cream to soften it up. -- ub |
From: Steve H. <dig...@da...> - 2013-09-16 12:39:07
|
The intended behavior should be the word behind/preceeding. With Ctrl, the Backspace key should simply take a bigger gulp. I'll look into this. I'm pleased to say that over the last few days I've gotten back into some new programming for Cream for the first time in years. I'm getting a new build system up and running and hope to release new Window Vim binaries and a new Cream version soon! -- Steve Hall [ digitect dancingpaper com ] |
From: Susan D. <Sus...@gm...> - 2013-09-15 12:24:59
|
Hi, Umberto, umberto boccioni wrote: > What is the intended behavior of Ctrl+Backspace in cream? The keyboard > shortcut page says the following: > > Ctrl+Backspace Delete word behind cursor > > ...but I find it deletes the following word. "the word following the cursor" is exactly what I expect when reading "word behind the cursor". Just my thoughts, Susan |
From: umberto b. <ve...@gm...> - 2013-09-15 10:38:21
|
What is the intended behavior of Ctrl+Backspace in cream? The keyboard shortcut page says the following: Ctrl+Backspace Delete word behind cursor ...but I find it deletes the following word. Is this the intended behavior but with inaccurate documentation, or am I simply misunderstanding the description? Shift+Backspace is also described as having the same function, but has the same behavior. I've come to use Ctrl+backspace all the time, so much so I don't even realize I'm using it, so it's tough to give up. Incidentally, I note there's no Ctrl+Delete, which would be the natural converse of Ctrl+backspace (and perilously close to ctrl+alt+del, though MS Word gets away with it) Apologies for the basic-ness of the question, but every couple years i dip back into vi and variants to try them out, but forget everything i learned in the interim. -- ub |
From: Indy S. <ms...@al...> - 2013-09-05 18:54:57
|
On Wed, Sep 4, 2013 at 6:14 PM, Steve Hall <st...@da...> wrote: > A patch would be accepted. It has been years since anyone on the Mac > platform expressed an interest in Cream, I'd be glad for some testing > and feedback. > Great. My vimscript isn't very deep, I've only ever made some syntax highlighting rules and setup some functions and status bars. Any ideas on how to get the value of rformat? I'm still another month out in getting some business issues sorted so > I can build binaries and get back to patching Cream again. Please > pardon the mess... > As for mac binaries, much like MacVim, I bet that the overlap between OS X users who want Cream and who are already running the open source code porting system brew is close to %100. It may be easier to get it accepted as a brew package and tell users to use brew rather than dive into the whole mac native *.app packaging or native installer framework. Especially because brew has some mechanisms to overriding Apple's local vim, which is fine release, but slightly behind, especially wrt ruby. If you were to use the mac native packaging you'd have to deal with overriding issues yourself. And as I <3 brew, I might even be interested in doing this. Or I could port Cream to iOS and put it in the app store. (Yes this is a joke, given that most non BSD open source licenses conflict with the App Store TOS. ) Indy -- Indy M. Siverd ms...@al... |
From: Steve H. <dig...@da...> - 2013-09-05 02:40:17
|
On Wed, Sep 4, 2013 at 6:38 PM, Indy Siverd <ms...@al...> wrote: > > Trying to get Cream working with MacVim (one of two mac vim porting > projects, this is the one that is still maintained). [...] > Also, if this is simple enough, I'll happily submit a diff with converted > icons and the three lines of code I suspect are needed to increase your > support of an "unsupported" MacVimCream. A patch would be accepted. It has been years since anyone on the Mac platform expressed an interest in Cream, I'd be glad for some testing and feedback. I'm still another month out in getting some business issues sorted so I can build binaries and get back to patching Cream again. Please pardon the mess... -- Steve Hall [ digitect dancingpaper com ] Cream for Vim (http://cream.sf.net) |
From: Indy S. <ms...@al...> - 2013-09-04 22:38:58
|
Hey folks, Trying to get Cream working with MacVim (one of two mac vim porting projects, this is the one that is still maintained). I've been a vi user for 20 years, and have done a fair amount of gvim on linux, but I'm trying to move my devel enviroment to OS X. I'm installing MacVim using brew, which puts the $VIMRUNTIME here: /usr/local/Cellar/macvim/7.3-66/MacVim.app/Contents/Resources/vim/runtime Which I had to force into $VRT in the INSTALL.sh script and it put things in the "right" place. It's working and cream comes up from the command line and has all the nice menu options and numbered buffers and colors. My next problem is that MacVim doesn't like *.xpm icons in the toolbar and would prefer *.png or *.tiff. Converting them is easy enough, but then I need to tell cream to use them instead. I found the following line in cream-cream-release.vim starting at line 174: execute ':' . mysilent . '!' . copycmd . ' ' . quote . cream_cvs . slash . 'addons' . slash . '*.vim' . quote . ' ' . quote . releasedir . slash . 'addons' . quote if rformat == "windows" let bitmap = '*.bmp' elseif rformat == "unix" let bitmap = '*.xpm' else let bitmap = '*.*' endif Inside cream I've run ":let" to look at the variables, but I don't see a value for "rformat" and I can't seem to get that "execute" to evaluate in ex mode, but I suspect this is because we're in level of vimscript here that is beyond my current skill. How can I find out the value of rformat on my system? Then I'm going to add let bitmap = '*.png' and see if everything is magically okay. Huh, I supposed I could try doing that in my own .creamrc, but that's not really the "right" way to solve this problem. Also, if this is simple enough, I'll happily submit a diff with converted icons and the three lines of code I suspect are needed to increase your support of an "unsupported" MacVimCream. Indy -- Indy M. Siverd ms...@al... |
From: Carsten A. <car...@go...> - 2013-07-23 18:55:16
|
Hello, apparently this same problem occurred previously (mail to this list by BPJ on 2011-5-17 and answer by Steve Hall), but the solution offered there does not work for me. The problem is: I installed a syntax highlighting file to ~/.vim/syntax and a filetype detect file to ~/.vim/ftdetect. When I open a file that fits the pattern, I get an error "E218: autocommand nesting too deep". The filetype detect command is "au BufNewFile,BufRead *.markdown,*.md,*.mkd,*.pd,*.pdc,*.pdk,*.pandoc,*.text set filetype=pandoc". As suggested by Steve, I tried inserting "nested" before "set", but the problem remains. The error does not occur with gvim or vim, and filetype autodetection works. Anything I can do to get rid of this? Thanks a lot, Carsten |
From: Maciej W <tri...@gm...> - 2013-07-23 11:42:25
|
Hello, Background: I was using Vim on Windows for some time now and wanted to install the lua_omni plugin (so that I'd have lua syntax folding working). After I've copied the files of the plugin to vim's directory and ran gVim, gVim told me that it: E370: Could not load library lua51.dll I've searched for lua51.dll on Google and downloaded ~4KB file from dllfiles.com. I've copied that file to %ProgramFiles%\vim\vim73 and %windir%\system32. Vim was still complaining for the *.dll file. I've tracked that the file that Vim was actually searching for was: lua5.1.dll , and not: lua51.dll (like the error message says) After downloading lua5.1.dll - this time, not from dllfiles.com, but from Lua's language website - copying the file to %programFiles%\Vim\vim73\ everything worked. Please fix the filename in the error message / provide list of dirs for which vim searches for the dll file in the error message if possible. I'm using Vim 7.3.829. Cheers. |
From: Clayton R. <cr...@sy...> - 2013-05-25 17:22:32
|
Howdy Steve, I just realized I should've sent this to the list, not directly to you. I apologize for that. Just want to let you know about a bug I'm seeing with macro record/play: Seen on both of the following system configurations: OS: Linux Mint 9 Cream: 0.42 VIM: 7.2 OS: WinXP Pro w/SP3 Cream: 0.42 VIM: 7.1 To reproduce: Use the text below, start at line 1 column 1, Shift+F8 (start record). 1) Control+Shift+Right to select "ALTER " 2) Delete 3) End 4) Backspace 5) Home 6) Down 7) Shift+F8 (end record) 8) F8 down through the remaining lines Before: ------- ALTER USER Annette IDENTIFIED BY 'Annette'; ALTER USER Warren IDENTIFIED BY 'Warren'; ALTER USER Anthony IDENTIFIED BY 'Anthony '; ALTER USER Preston IDENTIFIED BY 'Preston'; ALTER USER Kelly IDENTIFIED BY 'Kelly '; ALTER USER Taylor IDENTIFIED BY 'Taylor'; ALTER USER Stiller IDENTIFIED BY 'Stiller'; ALTER USER Dennis IDENTIFIED BY 'Dennis'; ALTER USER Schwart IDENTIFIED BY 'Schwart'; After: ------ USER Annette IDENTIFIED BY 'Annette' USER Warren IDENTIFIED BY 'Warren' AUSER Anthony IDENTIFIED BY 'Anthony ' AUSER Preston IDENTIFIED BY 'Preston' AUSER Kelly IDENTIFIED BY 'Kelly ' AUSER Taylor IDENTIFIED BY 'Taylor' AUSER Stiller IDENTIFIED BY 'Stiller' AUSER Dennis IDENTIFIED BY 'Dennis' AUSER Schwart IDENTIFIED BY 'Schwart' Notice the recorded Home key does not take the cursor home to column 1, but instead takes it to column 2. This macro works fine in VIM (qa ... @a). Thanks for your time, -Clay |
From: Oskar K. <tu...@gm...> - 2013-01-06 22:26:05
|
Yes, of coures. I should have mentioned it. On Fri, Jan 4, 2013 at 2:15 PM, Steve Hall <dig...@da...>wrote: > that this is a Ruby issue, not Vim |
From: Steve H. <dig...@da...> - 2013-01-04 01:10:17
|
On Jan 3, 2013 2:19 PM, "Oskar Kvist" <tu...@gm...> wrote: > > Hi! > > Check out this image: http://i.imgur.com/2FnVT.jpg?1 > > With recent versions of Vim without Cream the number of the current line is bold and yellow for me, as in the above image. With older versions and with the official Vim installer, that is not the case. And I have nothing in my colorscheme that tells it to appear like that. What's up? Not sure, what is the color scheme involved? I wonder if there isn't some newer feature of Vim that the color scheme is now able to use? -- Steve Hall [ digitect dancingpaper com ] |
From: Oskar K. <tu...@gm...> - 2013-01-03 19:19:34
|
Hi! Check out this image: http://i.imgur.com/2FnVT.jpg?1 With recent versions of Vim without Cream the number of the current line is bold and yellow for me, as in the above image. With older versions and with the official Vim installer, that is not the case. And I have nothing in my colorscheme that tells it to appear like that. What's up? |
From: Steve H. <dig...@da...> - 2013-01-03 14:47:11
|
On Thu, Jan 3, 2013 at 9:23 AM, Steve Hall <dig...@da...> wrote: > [...] > Sorry, took a closer look and fixed all this with a variable value adjustment. Please try the latest build and confirm if it fixed your issue: http://sourceforge.net/projects/cream/files/Vim/7.3.762/ -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim (http://cream.sourceforge.net) |
From: Steve H. <dig...@da...> - 2013-01-03 14:37:27
|
On Wed, Jan 2, 2013 at 10:21 PM, Oskar Kvist <tu...@gm...> wrote: > On Wed, Jan 2, 2013 at 7:44 PM, Oskar Kvist <tu...@gm...> wrote: > > > > Hi! > > I am having a great deal of trouble finding the correct version of > > Ruby to use with Vim without Cream version 7-3-744. > > > > :help ruby-dynamic says: > > > > >You need to install the right version of Ruby for this to work. > > >You can find the package to download from: > > >http://www.garbagecollect.jp/ruby/mswin32/en/download/release.html > > >Currently that is ruby-1.9.1-p429-i386-mswin32.zip Currently the > > >name is "msvcrt-ruby191.dll". > > > > But when I look in gvim.exe, it says msvcrt-ruby19.dll (notice > > 19.dll, not 191.dll). But I can't find a ruby version with that > > dll! Even version 1.9.0 has a dll named msvcrt-ruby190.dll. What > > should I do? > > I made this thread on SO that explains more what I've done. > http://stackoverflow.com/questions/14131750/cant-find-the-correct-version-of-ruby-for-vim-without-cream > > But I took a look at the release notes, and it says: > [...] > > Notice -DDYNAMIC_RUBY_DLL="msvcrt-ruby19.dll". I'm not sure if that > is the problem, but I think that might be wrong, because there is no > such file in ruby 1.9.1. Cream's Vim build was compiled with Ruby 1.9.3 from http://rubyinstaller.org/. For some reason, that distribution maintains the 1.9.1 file structure under bin/, include/, and lib/. I'm not much for tampering with defaults of dependency distributions or Vim's build process so this worked pretty much out of the box. It has been quite a while since the Vim build worked with Ruby, so perhaps the recent fixes didn't quite pick up the error your seeing? I might start by installing with that distro and putting on path. If that fails to help, I recommend taking your issue to the vim mailing lists (probably vim-dev) since they are the authors and maintainers of Vim and might understand how to help. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim (http://cream.sourceforge.net) |
From: Oskar K. <tu...@gm...> - 2013-01-03 03:21:45
|
I made this thread on SO that explains more what I've done. http://stackoverflow.com/questions/14131750/cant-find-the-correct-version-of-ruby-for-vim-without-cream But I took a look at the release notes, and it says: Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_HUGE -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL="perl58.dll" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL="python27.dll" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL="msvcrt-ruby19.dll" -DDYNAMIC_RUBY_VER=19 -DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL="lua51.dll" -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto -I/cygdrive/c/strawberry/perl/lib/CORE -I/cygdrive/c/Ruby193/lib/ruby/1.9.1/i386-mswin32 -I/cygdrive/c/Ruby193/include/ruby-1.9.1 -I/cygdrive/c/Ruby193/include/ruby-1.9.1/i386-mswin32 -I/cygdrive/c/PROGRA~2/Lua/5.1/include -s -mno-cygwin Notice -DDYNAMIC_RUBY_DLL="msvcrt-ruby19.dll". I'm not sure if that is the problem, but I think that might be wrong, because there is no such file in ruby 1.9.1. On Thu, Jan 3, 2013 at 1:44 AM, Oskar Kvist <tu...@gm...> wrote: > Hi! > > I am having a great deal of trouble finding the correct version of Ruby to > use with Vim without Cream version 7-3-744. > > :help ruby-dynamic says: > > >You need to install the right version of Ruby for this to work. You can > find > >the package to download from: > >http://www.garbagecollect.jp/ruby/mswin32/en/download/release.html > >Currently that is ruby-1.9.1-p429-i386-mswin32.zip > > >Currently the name is "msvcrt-ruby191.dll". > > > But when I look in gvim.exe, it says msvcrt-ruby19.dll (notice 19.dll, not > 191.dll). But I can't find a ruby version with that dll! Even version 1.9.0 > has a dll named msvcrt-ruby190.dll. What should I do? > > > > > |
From: Oskar K. <tu...@gm...> - 2013-01-03 00:44:26
|
Hi! I am having a great deal of trouble finding the correct version of Ruby to use with Vim without Cream version 7-3-744. :help ruby-dynamic says: >You need to install the right version of Ruby for this to work. You can find >the package to download from: >http://www.garbagecollect.jp/ruby/mswin32/en/download/release.html >Currently that is ruby-1.9.1-p429-i386-mswin32.zip >Currently the name is "msvcrt-ruby191.dll". But when I look in gvim.exe, it says msvcrt-ruby19.dll (notice 19.dll, not 191.dll). But I can't find a ruby version with that dll! Even version 1.9.0 has a dll named msvcrt-ruby190.dll. What should I do? |
From: Steve H. <dig...@gm...> - 2012-12-06 13:34:18
|
On Thu, Dec 6, 2012 at 4:58 AM, saeed bishara <sae...@gm...> wrote: > > I'm new user of cream, when I use the function prototype popup, > Alt+(, it works fine, but sometimes the function prototype is too > large to fit into the single line popup window, how can I make it > show full prototype? This would require a little work in Cream_pop_menu(). Vim's popup menu function only allows one line per entry. Cream could split function prototypes into as many lengths of x as required and enter each as a separate menu item. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim (http://cream.sourceforge.net) |
From: saeed b. <sae...@gm...> - 2012-12-06 09:58:56
|
Hi , I'm new user of cream, when I use the function prototype popup, Alt+(, it works fine, but sometimes the function prototype is too large to fit into the single line popup window, how can I make it show full prototype? thanks saeed |
From: Sascha H. <s....@pe...> - 2012-08-02 08:43:28
|
Hi Steve, On Wed, Aug 01, 2012 at 10:23:32AM -0400, Steve Hall wrote: > On Tue, Jul 31, 2012 at 3:44 AM, Sascha Hauer wrote: > > > > I'm a everyday user of cream and enjoy it very much. There's one > > thing that really nags me though: When I have many tabs open, then > > each time I close a tab cream internally seems to iterate over all > > opened tabs. This can take a very long time, with many documents > > opened it often takes up to 10s just to close a tab. > > > > Is there any way to get rid of this? I tried looking myself, but > > didn't find the place where this iteration happens. > > The code starts at Cream_close() in cream-lib.vim and references a > number of window and tab setup functions both here and in > cream-win-tab-buf.vim. > > The whole thing could use a good re-factoring because much of this > worked around bugs in Vim that may now be solved. Thanks for your help. I finally tracked down the guilty function. I removed the call to Cream_tabpages_refresh() from Cream_window_setup(), et voila, opening/closing documents is much smoother now. So far I haven't seen any negative impacts of doing so, but I don't know what the regressions could be. One thing I noticed is that when opening multiple documents with the --remote-tab-silent option is that the tabs appear as 'untitled' until they are first selected. That happens with or without my change though. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | |
From: Steve H. <dig...@da...> - 2012-08-01 14:37:15
|
On Tue, Jul 31, 2012 at 3:44 AM, Sascha Hauer wrote: > > I'm a everyday user of cream and enjoy it very much. There's one > thing that really nags me though: When I have many tabs open, then > each time I close a tab cream internally seems to iterate over all > opened tabs. This can take a very long time, with many documents > opened it often takes up to 10s just to close a tab. > > Is there any way to get rid of this? I tried looking myself, but > didn't find the place where this iteration happens. The code starts at Cream_close() in cream-lib.vim and references a number of window and tab setup functions both here and in cream-win-tab-buf.vim. The whole thing could use a good re-factoring because much of this worked around bugs in Vim that may now be solved. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim (http://cream.sourceforge.net) |