Org-mode mailing list
 help / color / mirror / Atom feed
From: Daimrod <>
To: "François Pinard" <>
Subject: Re: colorg: Some news!
Date: Mon, 21 Jan 2013 17:28:16 +0100
Message-ID: <87k3r6wlen.fsf@casa.home> (raw)
In-Reply-To: <> (=?utf-8?Q?=22Fran=C3=A7ois?= Pinard"'s message of "Mon, 21 Jan 2013 10:53:29 -0500")

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

François Pinard <> writes:

> Once we get a working solution, the protocol remains the contact point.
> The server could be replaced using other languages, and new clients may
> be written for other editors (given they are extensible enough).  My
> goal is quickly getting something usable, so I selected the means that
> looked fastest to me, and that's how Python got in the picture.
> Is there any incentive for rewriting the server in Emacs Lisp?  For one,
> even if rather bearable, Emacs Lisp is not my preferred programming
> language.  Moreover, I consider a bit wrong having to rely on an editor
> for tasks wholly unrelated to editing.  Other people are free to have
> differing opinions, and do that rewrite, however.

It's not unlreated to editing, it's for collaborative editing! :)
Anyway, I understand and respect your point of view.

Moreover, it's nice of you to report on the mailing list, it helps to
keep on eye.

> If I really had more time and less pressure, I would likely have
> selected Node (JavaScript) to write the server instead of Python.  The
> choice of JSON within the ColOrg communication protocol is a way, for
> me, to leave that door opened.  One not so hidden dream is to bring Org
> mode a bit closer to Web browsers, if there are ways to do so.


[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

      reply	other threads:[~2013-01-21 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  5:30 François Pinard
2013-01-21  5:50 ` Daimrod
2013-01-21 15:53   ` François Pinard
2013-01-21 16:28     ` Daimrod [this message]

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:

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

  git send-email \
    --in-reply-to=87k3r6wlen.fsf@casa.home \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone