Dear Uwe,
Le 27/10/2015 00:40, Uwe Stöhr a écrit :
Am 26.10.2015 um 17:21 schrieb Guillaume Munch:
The user reported two valid use cases that are exceptions to this
behaviour: \lstinline and \usepackage{bigfoot}. This used to work before
⇒ regression.
As I wrote, I don't agree. We had a val
Le 26/10/2015 20:52, Georg Baum a écrit :
Guillaume Munch wrote:
Dear Uwe,
Keywords regression removed
Status changed from assigned to closed
Resolution set to wontfix
Milestone 2.2.0 deleted
I don't think that we should support things that break compilation
with the default settings.
The
Am 27.10.2015 um 01:40 schrieb Uwe Stöhr:
If you want a proper fix, then we must automatically add the "inline"
option if a listings inset is placed into a footnote or margin note.
Hmm, this is no proper fix, since the user could remove the inline
option later on. He might have done hundred o
Am 26.10.2015 um 17:21 schrieb Guillaume Munch:
The user reported two valid use cases that are exceptions to this
behaviour: \lstinline and \usepackage{bigfoot}. This used to work before
⇒ regression.
As I wrote, I don't agree. We had a valid bug report where a user put a
listings inset in a
Guillaume Munch wrote:
> Dear Uwe,
>
>> Keywords regression removed
>> Status changed from assigned to closed
>> Resolution set to wontfix
>> Milestone 2.2.0 deleted
>>
>>
>> I don't think that we should support things that break compilation
>> with the default settings.
>
> Then maybe have list
Dear Uwe,
Keywords regression removed
Status changed from assigned to closed
Resolution set to wontfix
Milestone 2.2.0 deleted
I don't see a regression here. The point is that users insert
listings via the LyX menu or a shortcut. This inserts a lstlisting
environment that will not compile whe
