Thanks a lot Jürgen. The following insets do not have a ::latex implementation and thus are at a risk of dataloss in advanced s&r (although some of these maybe inherit it from some other one). Maybe the safest thing would be to implement Inset::latex that outputs some unmatchable string when the runparams.force_output flag is set. Would this be a good idea? How can I build an unmatchable string?
A/ ~/src/lyx/src/insets$ grep -L ::latex Inset*.cpp InsetBibitem.cpp InsetCollapsable.cpp InsetCommandParams.cpp Inset.cpp InsetERT.cpp InsetFlex.cpp InsetFootlike.cpp InsetGraphicsParams.cpp InsetLabel.cpp InsetListingsParams.cpp InsetMarginal.cpp InsetPreview.cpp InsetScript.cpp InsetTOC.cpp On Tue, Oct 14, 2014 at 11:37 PM, Jürgen Spitzmüller <sp...@lyx.org> wrote: > 2014-10-14 22:25 GMT+02:00 Alfredo Braunstein: >> >> Btw, are there other insets besides InsetNote that could produce no >> output? If the answer if yes, we could call the flag force_output or >> something and use it where needed. > > > Inactive branches, and maybe some kinds of FlexInsets. > > Jürgen > >> >> >> A/ > >
