Bo> This is what I tried to do at first. However, in lyx, every line
Bo> starts a new paragraph and you will get an extra newline between
Bo> your program code. This is hard-coded to lyx and I do not see a
Bo> good solution to this problem.
Adding a special layout flag to avoid this would be less work that a
new inset.
This is definitely doable but as I mentioned in another email, will
not handle all sort of listings parameters and float listings. And a
collapsible inset is better for long listings.
Also, a GUI to enter 130 different parameters by hand is
basically useless.
I agree that the GUI side is almost useless now but that can come
later because they will not change file format etc. The reason why I
want to put InsetListings in now is that if we do not do it now, it
has to wait till 1.6.0 because of the file format changes. If we can
decide now the very basic things:
1. whether or not use an inset for lstlisting
2. whether or not use the include dialog for lstinputlisting
we can put the current patch (or some other sort) in and advertise it
as an experimental feature. Then, all the improvements can come later
without file format change.
Could it just be a character style?
character style with a lot of options?
Bo
