On Fri, Sep 21, 2007 at 01:19:48AM +0200, Dov Feldstern wrote: > > > (changing the title, since it now sounds like this is really a separate > issue from Neal's original issue...) > > > Martin Vermeer wrote: > > > >The attached seems to fix it and has the merit of me sort of > >understanding why it works. > > > >- Martin > > > > Thanks, Martin! This does indeed fix the issue I was complaining about. > > In order that I also understand why it works --- what exactly is this > doDispatch function, when is it called?
Whenever you type something or press a mouse button, i.e., an LFUN should be "dispatched" i.e. handled. In this case it's the typing of characters that matters. > Now there's a follow-up issue: when leaving the ERT inset by pressing > right-arrow at the end of the inset, to get back outside after the > inset, the language is remaining "latex_language", which is wrong (for > example, if you view source you'll see that the encoding is being set to > latin1). So we're going to need some reverse mechanism of what your > current fix did. Yes, I see that too, but only if the ERT is at end of paragraph. > So here's my question: is there any function for jumping out of an inset > to immediately after the inset? from anywhere inside the inset? is there > an lfun/key-binding to such a function? LFUN_CHAR_FORWARD. But I suspect this is due to something Abdel removed... perhaps you should go though his patches here to find the culprit. > I think that there should be such a function if it doesn't yet exist > (and it would also prove useful to give users access to it --- > especially for bidi text, where getting out of an inset is not as > straightforward as you would think). And inside that function, we could > set the current font back to the font of the inset itself (which is > distinct from the font *inside* the inset, and is actually the font that > was active before the inset). Then that should fix this issue. > > Thanks! > Dov - Martin
