Uwe Stöhr wrote: > Am 21.02.2012 22:16, schrieb Georg Baum: > >>> With the module I could add >>> tex2lyx support for fancyvrb and thus fix the bug but I'm not sure if >>> this way is the best. Comments are welcome. >> >> Please fix the standard verbatim environment first before you add new >> things. > > The standard verbatim environment is not affected.
No, it is not. But IMHO it is not a good idea to start a new feature (verbatim), and then hop on to the next one (fancyvrb) while the first one is still very incomplete. The result will be very instable software if this happens too often. Besides that I still think that the endless loop should be fixed first. Without the module it is easy to reproduce, with the module it becomes more difficult. > tex2lyx can of course > not know what TeX code is verbatim and what not. For verbatim it now > knows, but for other verbatim environments it does not. In case no info is > available it of course treats it like any other code. So I don't see > another solution than to tell tex2lyx that code inside a Verbatim > environment also needs to be handled like verbatim. The usual solution to this kind of problem is not to tell tex2lyx, but to make use of the layout properties in tex2lyx (look where findLayout() is called). That way, a user can add modules for verbatim-like environments himself, whithout needing to change tex2lyx. Again, this is something already suggested by Jean-Marc. Please look in the cvs mailing list for his email. Georg
