Andre Poenitz wrote: >> That might be enough. But it's not clear to me if this causes problems >> with cut and paste. > > Sure there will problems, but right now we already have special handling > for e.g. and three hundred inset function or so taking a buffer
And what's the real problem with that? If DocIterator had a buffer_ member, we could just pass around a DocIterator & to inset functions that need the parent hierarchy. > argument. Also there are problems in mathed as there's no flawless > MathData -> string -> MathData due to unknown buffer settings. What was the reason for streaming into latex internally in mathed? I cannot remember. > So putting some extra work in the case of insets transefered across > buffers might be the smaller evil in the end. > > Yes, that's quite a bit of work, but something that has been in the back > of my mind for a while... Ugh. So you are planning to reintroduce back pointers? A/
