From: Richard M Stallman <rms@gnu.org>
To: Phil Hagelberg <phil@hagelb.org>
Cc: jtk@yahoo.com, emacs-devel@gnu.org
Subject: Re: obby
Date: Thu, 21 May 2009 14:35:39 -0400 [thread overview]
Message-ID: <E1M7D7D-0006Ju-8i@fencepost.gnu.org> (raw)
In-Reply-To: <873abbr4hp.fsf@hagelb.org> (message from Phil Hagelberg on Mon, 11 May 2009 09:25:38 -0700)
I had planned to revisit the problem once the new implementation of the
obby protocol and client (now called Infinote) had been released. But
implementing inclusion transformation is very difficult.
Can you tell us more about this problem?
By the way, this is a textbook case for why we would want to support
dynamic linking. The reference implementation of the Infinote protocol,
libinfinote, is released under the LGPL, so it would save a great deal
of effort to be able to use that rather than creating a new,
independent, under-manned implementation from scratch.
We could link with it non-dynamically too.
I don't understand the structure of the situation. Did you
reimplement the same thing in Lisp?
next prev parent reply other threads:[~2009-05-21 18:35 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 ` Richard M Stallman [this message]
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 ` obby Karl Fogel
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=E1M7D7D-0006Ju-8i@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jtk@yahoo.com \
--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.