Loading ...
Sorry, an error occurred while loading the content.
 

Re: Bug: Crash with too many statusline arguments

Expand Messages
  • Steve Hall
    Wow, thanks for looking that up! That s good information to know. Is it documented outside of the code? Never realized that closing the group was
    Message 1 of 4 , Mar 25, 2002
      Wow, thanks for looking that up! That's good information to know. Is
      it documented outside of the code?

      Never realized that "closing" the group was unnecessary. Been working
      with HTML 4.01/XML too long! This frees me up a bit now, although
      I could myself running into a 25*2 limit someday. ;)


      From: "Flemming Madsen" <fma@...>
      >
      > Just checked the code:
      >
      > There is currently allocated space for 50 statusline items and you
      > specify ~18*3 = 54
      >
      > Apparently the code will happily run past the end of that space
      >
      > Maybe you can shave off those %*'s at the end, when the hilight is
      > changed immediately afterwards anyway
      >
      > /Flemming
      >
      > digitect@... wrote:
      > >
      > > Hi all,
      > >
      > > I think I found a bug with the statusline. I've noticed that if I have
      > > too many arguments in the statusline, gVim 6.1b (on Win2K) crashes
      > > immediately on startup.
      > >
      > > Below is a sample statement. (I'm returning evaluated environmental
      > > conditions, where the statements return empty if false, an
      > > abbreviation if true, and are colored with different User1 groups
      > > depending; screenshot: http://cream.sourceforge.net/screenshot1.png .)
      > > I have to remove three of the lines below to avoid the problem.
      > >
      > > set statusline=
      > > \%3*%{Cream_statusline_filestate()}\ %*
      > > \%2*%t%*
      > > \%1*\ (%{expand(\"%:p:h\")})\ [%{Cream_statusline_fileformat()}]\ %=\|%*
      > > \%2*%{Cream_statusline_showON()}%*
      > > \%1*%{Cream_statusline_showOFF()}\|%*
      > > \%2*%{Cream_statusline_wrapON()}%*
      > > \%1*%{Cream_statusline_wrapOFF()}\|%*
      > > \%2*%{Cream_statusline_autowrapON()}%*
      > > \%1*%{Cream_statusline_autowrapOFF()}%*
      > > \%2*%{Cream_statusline_autowrap_widthON()}%*
      > > \%1*%{Cream_statusline_autowrap_widthOFF()}\|%*
      > > \%2*%{Cream_statusline_autoindentON()}%*
      > > \%1*%{Cream_statusline_autoindentOFF()}\|%*
      > > \%4*%{Cream_statusline_modeNO()}%*
      > > \%3*%{Cream_statusline_modeCOL()}%*
      > > \%1*%{Cream_statusline_modeOK()}\|%*
      > > \%1*%05(%l%),%03(%c%)%*
      > > \%2*\ %P\ %*
      > >
      > > Has anybody else experienced a similar problem?
      > >
      > > Steve Hall [ digitect@... ]
    Your message has been successfully submitted and would be delivered to recipients shortly.