> On Jun 2, 2019, at 2:50 AM, Enrico Forestieri wrote:
>
> On Sat, Jun 01, 2019 at 02:30:30PM -0700, list_em...@icloud.com wrote:
>>
>> I found the problem—it was a broken LyX pipe or something like that.
>> (I don’t understand this well.) I discovered that when LyX quit it was
>> leaving
> On Jun 4, 2019, at 07:37, Pavel Sanda wrote:
>
> Hi,
>
> could we make missing citation warning somehow more visible
> when they happen? We detect them from the log already,
> but we just color them in latex output window.
>
> I would like to have something more disturbing -
> e.g. red
On Tuesday, 4 June 2019 07.43.18 WEST Guenter Milde wrote:
> It *may* be required with Python 3.1, 3.2, 3.3, or 3.4.
> Unfortunately, I don't know whether `output` is of type "bytes" or
> "str" with this versions.
>
> If we can establish, that `output` is of type "str" in all Python versions
>
Hi,
could we make missing citation warning somehow more visible
when they happen? We detect them from the log already,
but we just color them in latex output window.
I would like to have something more disturbing -
e.g. red exlamation mark in status line (or better idea?).
We actually don't
On 2019-06-03, José Abílio Matos wrote:
> On Tuesday, 26 February 2019 12.15.06 WEST Guenter Milde wrote:
>> In any case, os.popen is deprecated since Python 2.6 and should be replaced
>> by calls to subprocess. https://docs.python.org/3/library/subprocess.html
> That is true but in a sense
On 2019-06-03, José Abílio Matos wrote:
> On Thursday, 28 February 2019 22.03.48 WEST Guenter Milde wrote:
>> >> diff --git a/lib/scripts/convertDefault.py
>> >> b/lib/scripts/convertDefault.py
>> >> index 8678965013..c7db4f5499 100644
>> >> --- a/lib/scripts/convertDefault.py
>> >> +++
