Further investigation reveals alternative routes of finding the language:
In InsetQuotes::Validate(LaTeXFeatures & features)
use
features.bufferParams().language
in place of current_view->buffer()->GetLanguage()
int InsetQuotes::Latex(Buffer const *, ostream & os,
bool /*fragile*/, bool) const
why not use the Buffer * that is passed but not used?
Angus
On Wed, 27 Sep 2000, Angus Leeming wrote:
> Several of the insets already store Buffer * buffer directly, this being
> passed to the inset through the constructor. If we do the same here and in
> insetref.[Ch], then NONE of the insets use current_view at all.
>
> Shall I do this?
>
> Angus
>
> On Wed, 27 Sep 2000, Andre Poenitz wrote:
> > The _only_ _two_ obstacles for batch export to any format without popping
> > up the GUI are around line 297 and line 236 in insets/insetquotes.C the
> > use of current_view to get the buffer's language
> > current_view->buffer()->GetLanguage().
> >
> > If this is replaced by "default", it works!
> >
> > Of course, "default" might not the right thing to use, so if anybody
> > could help me to find the language of the inset without using
> > "current_view", I'd be glad to prepare a patch that would add a feature I
> > have been missing for years...
> >
> > Andre'
> >
> > PS: Maybe someone more knowledgable could check whether the explicit use
> > of the buffer's language in these two places makes sense at all.
