all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thibaut Verron <thibaut.verron@gmail.com>
To: Robert Pluim <rpluim@gmail.com>, tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Org-Mode compared to Jupyter
Date: Fri, 4 Nov 2022 15:27:13 +0100	[thread overview]
Message-ID: <973dff6b-ed4d-f19c-486e-d7b93083ccb6@gmail.com> (raw)
In-Reply-To: <87sfiyizs8.fsf@gmail.com>

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





  parent reply	other threads:[~2022-11-04 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  8:14 Org-Mode compared to Jupyter Christopher Dimech
2022-11-04 11:16 ` Eric S Fraga
2022-11-04 11:36 ` Joost Kremers
2022-11-04 11:56   ` tomas
2022-11-04 14:01     ` Robert Pluim
2022-11-04 14:16       ` Joost Kremers
2022-11-04 14:32         ` Robert Pluim
2022-11-04 14:27       ` Thibaut Verron [this message]
2022-11-04 16:31       ` tomas
2022-11-04 17:24         ` Thibaut Verron
2022-11-05 13:56     ` Jean Louis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=973dff6b-ed4d-f19c-486e-d7b93083ccb6@gmail.com \
    --to=thibaut.verron@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=tomas@tuxteam.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.