[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Org-Mode compared to Jupyter
From: |
Thibaut Verron |
Subject: |
Re: Org-Mode compared to Jupyter |
Date: |
Fri, 4 Nov 2022 15:27:13 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 |
On 04/11/2022 15:01, Robert Pluim wrote:
On Fri, 4 Nov 2022 12:56:44 +0100, <tomas@tuxteam.de> said:
tomas> For me, this is actually the main disqualifier. There's no worse
nightmare
tomas> (for me) than editing text in a browser.
atomic-chrome solves that issue nicely.
Last time I checked (~2 years ago), it didn't solve the issue at all.
There were several flavors of such extensions, including atomic-chrome,
edit-with-emacs, ghosttext... Some of those only supported html
textareas (afaict that's still the case with atomic-chrome), making them
unusable for services like jupyter which don't use textareas.
Others did support some javascript editors including codemirror (thus
covering jupyter and overleaf at least). But in addition to that, as far
as I could tell jupyter was treating each line as a separate codemirror
field, which was completely breaking the emacs workflow -- regardless of
the extension.
That might have changed since then, of course.
Best wishes,
Thibaut