Empty lines are removed when importing into LyX-Code

[pelle@…]

When inserting "Plain Text as Lines" into a LyX-Code environment, empty lines are removed. This is clearly wrong.

Debian bug: ​http://bugs.debian.org/187500

[Uwe Stöhr]

Confirmed; when text is imported as lines into a LyX-code, LyX-note,
LyX-comment, or LyX-gray text environment, empty lines shouldn't be deleted.

[Richard Heck]

Moving all bugs targeted to before 1.5.0 to 1.5.x.

If these are yours, please check that they have not been fixed and, if so, close
them.

Otherwise, sorry for the spam.

[Juergen Spitzmueller]

1.5.x is frozen. Shifting all 1.5.x-targetted bugs to 1.6.x.

If you have reported this bug, please verify if it still occurs in 1.6.0 and
close the report, if not.

[Richard Heck]

Doing this correctly means adding an InsetLayout tag that would tell us whether to preserve blank lines, I think.

[lasgouttes]

Why an InsetLayout? There is no inset except lyx notes mentionned by Uwe (but in this cases it is normal to remove empty lines)

Concerning plain layouts, we have the KeepEmpty tag that can be used.

[Uwe Stöhr]

too late for LyX 2.1

[lasgouttes]

Let's come back to this oldish bug. The bug still stands, but we already honor KeepEmpty as we should. The funny thing is the LyX-Code does not have KeepEmpty set to 1. When one inserts into an ERT inset, everything is fine.

So the question is whether we shall set keepempty=1 for LyX-Code. One problem with that is that it does not honor multiple consecutive empty lines. But this may not be a very big problem.

[lasgouttes]

So what shall I do? Close the bug as invalid or change the definition of LyX-Code? I have verified that the code is actually correct (although it should respect allowMultipar() --- I have a fix for that).

As for LyX-Code, it should be killed in favor of alltt, although I do not know whether it would change document layout a lot.

[Richard Heck]

Not sure. I don't use that layout myself, so I have no strong view. Do as you think best, it seems to me.

[Juergen Spitzmueller]

Replying to lasgouttes:

As for LyX-Code, it should be killed in favor of alltt, although I do not know whether it would change document layout a lot.

We could do the change and retain the old LyX-Code (via local layout) for old documents, but do not provide it anymore for new ones.

[Scott Kostyshak]

JMarc anything you want to do with this for 2.2.0?

[Scott Kostyshak]

CC'ing JMarc. Since no one else gave an opinion, I suggest as Richard to do as you think best.

[lasgouttes]

Getting rid of LyX-Code would be nice indeed. This is a remnant of the past. I don't know how to do what Juergen proposes, though.

[Scott Kostyshak]

Time is running out if we want to solve this for 2.2.0.

[Scott Kostyshak]

Jürgen does not have any time and it seems he is the only one that might fix this. I will put this as 2.3.0 since it seems there is agreement on what to do (get rid of LyX-Code but retain the old LyX-Code (via local layout) for old documents.

[lasgouttes]

Instead of a local layout it may be better to use a module.

[Scott Kostyshak]

Is anyone planning to work on retiring LyX-Code for 2.3.0?

[lasgouttes]

Not me unfortunately.

[Scott Kostyshak]

I don't see any recent work in progress for this bug. I'm removing the milestone. If anyone would like to work on this for 2.4.0, please let me know as soon as possible and set the milestone to 2.4.0 so we can discuss it.