all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <karl.fogel@canonical.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: jtk@yahoo.com, Phil Hagelberg <phil@hagelb.org>, emacs-devel@gnu.org
Subject: Re: obby
Date: Mon, 25 May 2009 16:45:11 +0200	[thread overview]
Message-ID: <87iqjp9r7s.fsf@canonical.com> (raw)
In-Reply-To: <jwvy6sm56t0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 24 May 2009 21:11:05 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The problem goes a bit further: most distributions, like Debian and
> friends, will find it inconvenient to build their Emacs binary against
> that library unless that library is small, or it's likely to already be
> installed, or most Emacs users are likely to want to use it.
> In the case of support for `obby', I don't know the size of the library,
> but at least I don't expect most Emacs users to use it, and I don't
> expect most installs to already have the library installed.

The library is about 2.8M in source release.  It's C++.
(Obtained from http://gobby.0x539.de/trac/wiki/Download)

> That's a significant problem for "static linking" (it's actually still
> dynamically-linked by the way, altough the list of libraries thus linked
> is known statically).

Until the library is widely distributed, we could just ship its source
in Emacs (the same way other programs do with SQLite, for example).
Well, 2.8M is a lot to just support one feature; I'm not sure what our
standards are for decisions like this.

But could we conditionally link against it?  Use it if it is there, and
have Ebby simply return errors otherwise, while the rest of Emacs would
be unaffected?

The reason I'm interested is that Gobby, the program for which the
'obby' protocol was invented, is getting quite popular.  I'm sitting
right now at a conference where it's the conference-wide default for
collaborative editing, and this is not the first time that's happened.
If this protocol is going to become a standard for collaborative editing
(as seems likely, at least from here) then it could be a big win for
Emacs to support it.

I can't devote development time to this myself, so I'm cheering for
anything that makes it easier for Phil Hagelberg to work on it :-).

-Karl




  reply	other threads:[~2009-05-25 14:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 19:53 obby Richard M Stallman
2009-05-10 21:29 ` obby Jeff Kowalczyk
2009-05-11 14:35   ` obby Jeff Kowalczyk
2009-05-11 16:25   ` obby Phil Hagelberg
2009-05-11 17:19     ` obby Stefan Monnier
2009-05-11 18:25       ` obby joakim
2009-05-13  9:13         ` obby Richard M Stallman
2009-05-13  9:53           ` obby joakim
2009-05-13 22:34             ` obby Richard M Stallman
2009-05-21 18:35     ` obby Richard M Stallman
2009-05-22 11:41       ` obby Christian Lynbech
2009-05-22 16:45         ` obby Phil Hagelberg
2009-05-23 15:38         ` obby Richard M Stallman
2009-05-22 16:42       ` obby Phil Hagelberg
2009-05-23 14:32         ` obby Karl Fogel
2009-05-25  1:11           ` obby Stefan Monnier
2009-05-25 14:45             ` Karl Fogel [this message]
2009-05-25 15:02               ` obby Stefan Monnier
2009-05-23 15:38         ` obby Richard M Stallman
2009-05-11 21:08   ` obby Richard M Stallman

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=87iqjp9r7s.fsf@canonical.com \
    --to=karl.fogel@canonical.com \
    --cc=emacs-devel@gnu.org \
    --cc=jtk@yahoo.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=phil@hagelb.org \
    /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.