Cream (for Vim)

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)

Maurits Lamers <mauritslamers@...> writes:

> 
> Hi all,
> 
> I installed Cream under Ubuntu 12.04 64bit a few days ago and I have found
that the Open File Explorer doesn't
> seem to work.
> Any idea how I can 'fix' this?
> 
> Another thing: how difficult would it be to have a directory tree view in
cream that is graphical? I know
> plugins like NERDTree etc, but they are all in text mode, which takes way too
much space on the screen and to
> me they don't feel intuitive in a graphical environment (right-click-≥create
file or similar functionality).
> 
> greets
> 
> Maurits
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
Thank you for trying Maurits

I also want Cream on Ubuntu 12.04, but from past experience find non 12.04
compilations don't work. I have searched everywhere to find out when a version
of Cream for 12.04 will be available or how to make a previous version work, but
had no luck (just problem reports). 

Sorry I am no help, but I support your quest and hope someone has an answer.

Alan

On Thu, Jul 19, 2012 at 1:03 AM, A.Belle wrote:
> Maurits Lamers <mauritslamers@...> writes:
> >
> > I installed Cream under Ubuntu 12.04 64bit a few days ago and I
> > have found that the Open File Explorer doesn't
> > seem to work. Any idea how I can 'fix' this?
>
> I also want Cream on Ubuntu 12.04, but from past experience find non
> 12.04 compilations don't work. I have searched everywhere to find
> out when a version of Cream for 12.04 will be available or how to
> make a previous version work, but had no luck (just problem
> reports).
>
> Sorry I am no help, but I support your quest and hope someone has an
> answer.

It should be as easy as installing vim-X11, downloading the zip file:

http://sourceforge.net/projects/cream/files/Cream/0.43/cream-0.43.tar.gz/download

and running

  #sh INSTALL.sh

If Ubuntu has been following my Fedora's adjustment of .desktop file
architecture, you may find the application/icon broken but "cream"
should work from a terminal.

Please offer suggestions on how to improve this installer so it works
across distributions and versions.

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream for Vim (http://cream.sourceforge.net)

On Sat, Jun 9, 2012 at 7:02 AM,  <theorik@...> wrote:
>
> As far as I can see, the Python support built into vim is quite up to
> date, but the Perl support is quote outdated. Is this on purpose?

Not really, I build on a Win7 x64 system and there seems to be a lot
of issues with library support related to Vim on Windows. I
occasionally update packages and then find Vim doesn't support the
latest version and have to downgrade. Ruby currently has this issue,
I'm unable to find a library that Vim will build on.

I'll try a later Perl and if it works you'll see it in the next build.
:)


-- 
Steve Hall  [ digitect dancingpaper com ]
  Cream for Vim    http://cream.sourceforge.net

On Mon, Apr 2, 2012 at 7:06 AM, thomas@... <thomas@...> wrote:
>
> I used to use the "Vim without Cream" builds for Windows due to its
> support for Ruby ("ruby/dyn") among other things. Unfortunately, the
> Ruby bindings are not included in the newer builds, the last
> available build with it is 7.3.289 (as far as I can see). Is there a
> special reason why the newer builds are compiled without Ruby
> support? Would you mind compiling new builds with "ruby/dyn" again?

Something changed with Ruby and Make_cyg.mak about a year ago that
broke my build process and I've never been able to fix it. For some
reason it won't find Ruby. Same with MZSCHEME and TCL.

I've emailed the Vim list to see if I can get some help. I'd like to
make as many features available that we can.

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream for Vim (http://cream.sourceforge.net)

On Sat, 2011-11-26 at 13:28 +0800, Jonathan Pares wrote:
> 
> I'm new with Cream and I can say that I like it. There is may be one
> thing I'd like in addition is the possibility to have a file browser
> on the left side of the window. Is it possible ? If yes, how could I
> get it ?

You should find that Cream respects drag and drop from a nearby file
browser of your operating system. From a project perspective, this is
the most reliable way to provide the feature.

At one point Cream did provide an in-built browser in the form of the
opsplorer tree file explorer plugin:

http://www.vim.org/scripts/script.php?script_id=362

IMO, it was the best of all the plugins out there trying to do similar
things. But Vimscript is not a good tool for processing operating
system paths and files. It uses extreme text parsing and has a lot of
opportunities for bugs, especially across platforms and with filenames
that include non-alphanumeric characters. In an effort to keep the
project on track, I eventually removed it.

Vim has this same type of "feature" included in the form of the netrw
plugin. It too has lots of bugs when used outside of a very controlled
environment. I've never been able to use it on Windows or across a
network connection. I became frustrated with its feature creep over
basic stability and gave up trying to climb the mountain to
incorporate it into Cream.

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream for Vim          http://cream.sourceforge.net

> I'd be willing to add these to Cream if other users request, we can get
> permission, and I can find time to add the Cream custom (statusline)
> items. :)

Well, my hand is raised in "aye" if that counts for anything ;-)

-matt

Hi Steve,

You got it right. I have removed the plugins "snipmate" and "supertab" and
now the tab and shift+tab work ok.

Thanks,
 Jachym

On Tue, May 10, 2011 at 3:07 PM, Steve Hall <digitect@...:

> From: Joakim, Tue, May 10, 2011 6:36 am
> >
> > I believe that cream is getting the signals correctly because the
> > information on the line under the status line changes for tab and
> > shift+tab: =<SNR>96_SuperTab('n') and =<SNR>96_SuperTab('p')
> > respectively.
>
> There's the problem. This is a not a Cream function, there must be a
> plugin interfering somewhere. Use:
>
>  <Ctrl+L>:scriptnames<Enter>
>
> or grep through your plugins/ directory to find the file containing
> "SuperTab". (It could be in ~/.vim or in /usr/share/vim/ .) It likely
> has a mapping for <S-Tab>. You either need to remove the plugin or
> comment out that line to test.
>
>
> --
> Steve Hall  [ digitect dancingpaper com ]
> :: Cream for Vim (http://cream.sourceforge.net)
>
>
>

Hi Steve,


> Did your window manager/desktop environment version change? It's
>

Yes, I have updated openSUSE and there is KDE 4.6 in the current release.
Before I was using some older version of KDE.


>
>  :map <C-Tab>
>
> Cream should report:
>
>  v <C-Tab>  :<C-U>call Cream_nextwindow()<CR>
>
>
Yes, this returns the message it is supposed to return, as well as it shows
mapping for <S-Tab>. However, pressing Shift+Tab does the same thing as
pressing Tab only. This is weird because for example in KWrite, Shift+Tab
unindents normally...

Joakim

On Mon, 2011-05-09 at 15:38 +0200, Joakim wrote:
> 
> > Did your window manager/desktop environment version change? It's
> 
> Yes, I have updated openSUSE and there is KDE 4.6 in the current
> release. Before I was using some older version of KDE.
> 
> > :map <C-Tab>
> > 
> > Cream should report:
> > 
> > v <C-Tab>  :<C-U>call Cream_nextwindow()<CR>
> 
> Yes, this returns the message it is supposed to return, as well as
> it shows mapping for <S-Tab>. However, pressing Shift+Tab does the
> same thing as pressing Tab only. This is weird because for example
> in KWrite, Shift+Tab unindents normally...

There a plenty of reasons this could be, let's divide into two
categories:

1. gVim: Are you using the distributed build? Does the :version info
   show a Large or Huge build? Any chance some needed feature wasn't
   built into your gVim? Can you try a more feature-full build?

2. OS: Do you have many customizations in your KDE? Any chance your
   keyboard or language setting might be interfering? How about Alt or
   CapsLock remappings? Can you check that there isn't something
   special KDE uses Shift+Tab for? (And that a KDE app like KWrite may
   have accommodated?) For example, on Windows, Alt+F4 is reserved by
   Windows so it is impossible for Cream to use it.

I bet the problem is related to one of these. :)

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream for Vim          http://cream.sourceforge.net

Hi,

1. gVim: Are you using the distributed build? Does the :version info
>   show a Large or Huge build? Any chance some needed feature wasn't
>   built into your gVim? Can you try a more feature-full build?
>

I am using the huge build as provided in openSUSE. The output of :version is
at the end of this email.


> 2. OS: Do you have many customizations in your KDE? Any chance your
>   keyboard or language setting might be interfering? How about Alt or
>   CapsLock remappings? Can you check that there isn't something
>   special KDE uses Shift+Tab for? (And that a KDE app like KWrite may
>   have accommodated?) For example, on Windows, Alt+F4 is reserved by
>   Windows so it is impossible for Cream to use it.
>

Similarly, I use a pretty standard setting of KDE (English). Moreover, all
settings I use are the same as I used to use for the previous version of
KDE. I believe that cream is getting the signals correctly because the
information on the line under the status line changes for tab and shift+tab:
=<SNR>96_SuperTab('n') and =<SNR>96_SuperTab('p') respectively. It should be
just something in the settings or I do not understand the expected behavior
of Cream correctly.

If I press tab or shift+tab in a python file, is Cream supposed to
indent/unindent the selected block? This does not seem to be happening.

Thanks,
 Joakim




 :version

VIM - Vi IMproved 7.3 (2010 Aug 15)
Included patches: 1-62
Compiled by 'http://www.opensuse.org/'
Huge version without GUI.  Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con
+diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi
 +file_in_path +find_in_path +float +folding -footer +fork() +gettext
-hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap -lua +menu +mksession
+modify_fname +mouse -mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm
+mouse_netterm
 -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme
+netbeans_intg -osfiletype +path_extra +perl +persistent_undo +postscript
+printer
+profile +python -python3 +quickfix +reltime +rightleft +ruby +scrollbind
+signs +smartindent +sniff +startuptime +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse
+textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
+X11 +xfontset -xim +xsmp_interact +xterm_clipboard -xterm_save
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/etc"
 f-b for $VIMRUNTIME: "/usr/share/vim/current"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -fmessage-length=0 -O2
-Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-
unwind-tables -g -Wall -pipe -fno-strict-aliasing -fstack-protector-all
-I/usr/include  -D_LARGEFILE64_SOURCE=1
Linking: gcc   -L.  -rdynamic -Wl,-export-dynamic  -Wl,-E
-Wl,-rpath,/usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE
-L/usr/local/lib -Wl,--as-
needed -o vim    -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lnsl
-lncurses -lacl -lattr -lgpm -ldl    -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.12
.3/x86_64-linux-thread-multi/CORE  -L/usr/local/lib64 -fstack-protector
-L/usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE -lperl -lm -ldl
-lcryp
t -lpthread -L/usr/lib64/python2.7/config -lpython2.7 -lpthread -ldl -lutil
-lm -Xlinker -export-dynamic  -L/usr/lib64 -ltcl8.5 -ldl -lieee -lm -Wl,-R
 -Wl,/usr/lib64 -L/usr/lib64 -lruby -lrt -ldl -lcrypt -lm