Ben, for now, you might try redefining these two functions in
$CREAM."cream-user.vim" or in the Cream_conf_override() of a
system-wide cream-conf:
function! Cream_statusline_filestate()
return ""
endfunction
function! Cream_titletext()
...
let mymod = ""
...
endfunction
Then they will overwrite the corresponding Cream functions until
somebody finds time to write a patch for this. :)
--
Steve Hall [ digitect dancingpaper com ]
:: Cream... usability for Vim
:: http://cream.sourceforge.net
On Tue, 2007-09-04 at 11:01 -0300, Ben Armstrong wrote:
> Remember this one, Steve? Well, when we upgraded recently to 0.39,
> this broke again, so I had to reapply your fix. It would be nice if
> this could be implemented as a "performance feature" as you
> suggested so I wouldn't have to carry the patch forward from version
> to version.
>
> Thanks,
> Ben
>
> Steve Hall wrote:
> > On Thu, 2005-09-08 at 08:38 -0300, BG - Ben Armstrong wrote:
> >
> > > On Wed, 2005-09-07 at 17:25 -0400, Steve Hall wrote:
> > >
> > > > Cream tries to display the read-only status of a file in two
> > > > places: the statusline and the window title. If you test:
> > > >
> > > > set statusline&
> > > > set titlestring&
> > > >
> > > > in your cream-user, you should see this problem go away.
> > > >
> > > > Does that work?
> > > >
> > > That's it! Thanks. Looking forward to a proper fix so I can
> > > deliver this to my users. Obviously not having the status line
> > > at all is a Bad Thing. :)
> > >
> >
> > A good temporary solution would be:
> >
> > 1. Add a line at the top of cream-statusline function
> > Cream_statusline_filestate() to:
> >
> > return ""
> >
> > 2. Replace the cream-settings function Cream_titletext() lines:
> >
> > " modified
> > if getbufvar(mybufnr, "&modified") == 1
> > let mymod = "*"
> > else
> > let mymod = ""
> > endif
> >
> > to
> >
> > let mymod = ""
> >
> > I suppose we could make these automatic with some cream-conf var.
> > But I've also been thinking about adding "performance settings"
> > for large or high latency files. They could be meta controls for
> > items like those above, as well as &lazyredraw, &swapfiles,
> > &backup, :syntax and whatever else typically causes performance
> > problems in select situations.
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
cream-general mailing list
cream-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cream-general
