Lars Gullik Bjønnes wrote: > | So I have a copy of pybliographer (say) that hasn't kept up with > | the changing LyX syntax and the first time I use it I crash LyX? >> > | You're absolutely barking mad if you think that will improve the > | public perception of our rock-solid piece of software! > > Have you gone bonkers? > > Where did you get the faulty kb_action from? and why is it used to > call the haveFlag function? This function should not have been > called in the first place. > > Has nothing to do with external programs at all.
Well at the moment it has everything to do with an external program. If you're saying that such commands should be filtered out before they get to the ASSERT, then that's fair enough, but some work is needed because at the moment I can trigger the ASSERT as simply as this: $ echo 'LYXSRV:angus:hello' > ~/.lyx-1.4.x/server.in $ echo 'LYXCMD:angus:file-open:docs/UserGuide.lyx' > ~/.lyx-1.4.x/server.in $ echo 'LYXCMD:angus:exit' > ~/.lyx-1.4.x/server.in $ Assertion triggered in bool LyXAction::funcHasFlag(kb_action, LyXAction::func_attrib) const by failing check "ici != lyx_info_map.end()" in file ../../src/LyXAction.C:370
