From: Thibaut Verron <thibaut.verron@gmail.com>
To: tomas@tuxteam.de
Cc: Robert Pluim <rpluim@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Org-Mode compared to Jupyter
Date: Fri, 4 Nov 2022 18:24:17 +0100 [thread overview]
Message-ID: <CAFsi02RHsjth4DqVLL9=6+bQbeEm7Aduh1_kgrbs5u8XDfpxsw@mail.gmail.com> (raw)
In-Reply-To: <Y2U+fEtnldmpqzAV@tuxteam.de>
Le ven. 4 nov. 2022 à 17:33, <tomas@tuxteam.de> a écrit :
> On Fri, Nov 04, 2022 at 03:01:59PM +0100, 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.
>
> Atomic-chrome, which is presumably based on Atom, which is based on
> Electron, which is, after all, a big honkin' web browser in disguise.
>
Very confidently very wrong. ;)
As much as "it's all text" is "based on emacs": atomic-chrome is a chrome
browser extension allowing to edit textareas with atom.
And, relevant for the discussion here, the same browser extension can
interact with similar extensions for other editors, including Emacs.
> One authored by Google, no less.
>
Isn't Atom a product of Github, and therefore technically authored by
Microsoft?
Best wishes,
Thibaut
next prev parent reply other threads:[~2022-11-04 17:24 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
2022-11-04 16:31 ` tomas
2022-11-04 17:24 ` Thibaut Verron [this message]
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='CAFsi02RHsjth4DqVLL9=6+bQbeEm7Aduh1_kgrbs5u8XDfpxsw@mail.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.