Jean-Marc Lasgouttes wrote:
>>>>>> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>
>>> Inset::MARGIN_CODE), > InsetName("float", Inset::FLOAT_CODE),
>
> Bo> ERT_CODE dictates verbatim output which is exactly what
> Bo> InsetListings needs. I do not see a need for Inset::LISTINGS_CODE
> Bo> right now but this may turn out to be wrong.
>
> Please NO! ERT_CODE identifies the ERT inset and nothing else. If some
> lazy programmer decided to hardcode some behaviour depending on ERT, I
> think now is the right time to cleanup the code (assuming that we
> really thing adding listings is a good idea of course) and add the
> relevant methods.
i understand that some people really like this, but then again there are many
other things that people like as well.
implementing this properly will take time. moreover, we might need an extra
beta to test it properly as well.
so why don't we postpone this listings business until 1.6?
