From: Peter Lee <pete_lee@swbell.net>
Subject: Re: ELisp as a generic COM Client?
Date: Wed, 03 Sep 2003 22:10:00 GMT [thread overview]
Message-ID: <un0dlzfpp.fsf@swbell.net> (raw)
In-Reply-To: u7k4pfudn.fsf@jasonrumney.net
>>>> Jason Rumney writes:
Jason> You can do what you like with your own copy of Emacs, but I
Jason> don't think linking with most COM obects would be
Jason> compatible with the GPL.
Why not? You don't link with COM objects, but even if you did, I'm
not sure why it would be against the GPL.
As to the topic, a while back I wanted to be able to instantiate and
call into a COM object from Emacs and ended up creating a plugin based
on Steve Kemp's work:
http://www.emacswiki.org/cgi-bin/emacs/DynamicallyExtendingEmacs
Within the plugin I did what I wanted, which was basically the
automation of msdn for context sensitive help.
next prev parent reply other threads:[~2003-09-03 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 15:33 ELisp as a generic COM Client? Siegfried Heintze
2003-09-03 21:01 ` Kevin Rodgers
2003-09-03 21:13 ` Jason Rumney
2003-09-03 22:10 ` Peter Lee [this message]
2003-09-17 20:31 ` Kai Grossjohann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=un0dlzfpp.fsf@swbell.net \
--to=pete_lee@swbell.net \
/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.
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).