On Fri, Jun 06, 2003 at 03:37:36PM +0200, Lars Gullik Bj?nnes wrote:
> Strawberry ice-cream
, ice cream...
> ERT and CODE have different needs. ERT should IMHO ideally just
> have a plain vector > as backend, no paragraphs
> nothing, just what a plain old (eve
On Friday 06 June 2003 14:32, John Levon wrote:
>
> But it seems pointless anyway, math doesn't work properly in alltt :(
Ok, I got the picture. I have the same problem with docbook and Code. When
you have some solution for it I would like to help. :-)
> regards
> john
--
José Abílio
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Jun 06, 2003 at 05:29:33AM +0100, John Levon wrote:
|
| > o extra newline between pars. I suspect we need some handling in
| > TeXOnePar but that sounds hacky
| > o we can trivially allow insets such as insetref OK I think
|
| Updated patch appe
On Fri, Jun 06, 2003 at 02:24:29PM +0100, Jose' Matos wrote:
> Usual request, tell me how it looks and how do you want it to look. :-)
-\layout LyX-Code
+\layout Standard
+
+\begin_inset Code
+status Open
+
+\layout Standard
This is code
+\end_inset
+
+
But it seems pointless anyway, math do
On Friday 06 June 2003 14:14, John Levon wrote:
>
> Yes please ...
Usual request, tell me how it looks and how do you want it to look. :-)
> regards
> john
--
José Abílio
On Fri, Jun 06, 2003 at 05:29:33AM +0100, John Levon wrote:
> o extra newline between pars. I suspect we need some handling in
> TeXOnePar but that sounds hacky
> o we can trivially allow insets such as insetref OK I think
Updated patch appended. Please try it out ...
regards
john
code2.diff
On Fri, Jun 06, 2003 at 09:25:40AM +0100, Jose' Matos wrote:
> > o lyx2lyx stuff needed
>
> Do you want any help with this?
Yes please ...
regards
john
On Friday 06 June 2003 05:29, John Levon wrote:
> Here's a rough and unready start on insetcode. Try it with "code-insert"
>
> Issues :
...
> o lyx2lyx stuff needed
Do you want any help with this?
> Comments ? Suggestions ?
Good work. :-)
> regards
> john
--
José Abílio
Here's a rough and unready start on insetcode. Try it with "code-insert"
Issues :
o extra newline between pars. I suspect we need some handling in
TeXOnePar but that sounds hacky
o we can trivially allow insets such as insetref OK I think
o footnote is more difficult due to the "%\n" string.
