Am 06.07.2019 um 11:57 schrieb Jürgen Spitzmüller :
>
> Am Mittwoch, den 03.07.2019, 15:53 -0400 schrieb Richard Kimberly Heck:
>> Same problem. I've traced it to:
>>
>> \def\input@path{{/home/rikiheck/this~silly~dir/}}
>>
>> It appears to be that LaTeX itself has problems with such paths. If
The proper way to establish communication is to use ZeroMQ to interact with
IPython directly from LyX. I read the jupyter docs, it is something we could
try to do. I can communicate with the LyX main buffer now by letting the main
Browser to as ccess LyX.h, and thus have access to call
On 7/6/19 5:57 AM, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 03.07.2019, 15:53 -0400 schrieb Richard Kimberly Heck:
>> Same problem. I've traced it to:
>>
>> \def\input@path{{/home/rikiheck/this~silly~dir/}}
>>
>> It appears to be that LaTeX itself has problems with such paths. If
>> we
>> add
>This is a reply to Joel the comment.<
Hi Joel
Thanks for your input. The variable capture function feature is cool. I
didn't think of that. It could be implemented in two ways in my opinion.
(A). It could be done by using Jupyter lab's variable explorer extension.
It is already implemented there.
On Tue, Jul 2, 2019 at 11:03 AM Jason Sun wrote:
> I have built an example prototype widget that tries to combine LyX and
> Jupyter Notebook together.
>
> Is it implemented via QtWebEngine. Basically, by embedding a mini webpage
> browser inside LyX.
>
> A screenshot is here:
>
Am Mittwoch, den 03.07.2019, 15:53 -0400 schrieb Richard Kimberly Heck:
> Same problem. I've traced it to:
>
> \def\input@path{{/home/rikiheck/this~silly~dir/}}
>
> It appears to be that LaTeX itself has problems with such paths. If
> we
> add \detokenize:
>
>
