emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: TRS-80 <lists.trs-80@isnotmyreal.name>
Cc: emacs-orgmode@gnu.org
Subject: Re: Google Docs now supports MarkDown, but not Org syntax
Date: Sat, 11 Jun 2022 15:48:21 +0300	[thread overview]
Message-ID: <YqSPFcycHzvKw9e7@protected.localdomain> (raw)
In-Reply-To: <87y1zg24m0.fsf@isnotmyreal.name>

* TRS-80 <lists.trs-80@isnotmyreal.name> [2022-05-05 03:42]:
> Ken Mankoff <mankoff@gmail.com> writes:
> > Google Docs now supports MarkDown, not Org syntax :(.
> >
> > https://workspaceupdates.googleblog.com/2022/03/compose-with-markdown-in-google-docs-on.html

Google Docs is anyway proprietary Javascript software, it is not good
to drive users into it.

> There is a Free Software (AGPL3.0) alternative to Google Docs called
> HedgeDoc.  We have used it a little bit (within Armbian project) and I
> think it's pretty neat! [0]

I am just looking into:

HedgeDoc - The best platform to write and share markdown.

It is good for Markdown, but nothing similar to Google Docs, I can't
say it is alternative.

However, it would be good if HedgeDoc starts supporting Org mode, then
it would become very interesting. It is not hard really to support the
basics of Org. Can you do something about it?


Take action in Free Software Foundation campaigns:

In support of Richard M. Stallman

  reply	other threads:[~2022-06-11 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 13:56 [O] Google Docs now supports MarkDown, but not Org syntax Ken Mankoff
2022-05-05  0:41 ` TRS-80
2022-06-11 12:48   ` Jean Louis [this message]
2022-06-18  6:46     ` Ihor Radchenko

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=YqSPFcycHzvKw9e7@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=lists.trs-80@isnotmyreal.name \


* 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 public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).