From: googleartist@yahoo.com (Artist)
Subject: Re: Emacs as platform for the application
Date: 20 Sep 2002 08:34:20 -0700 [thread overview]
Message-ID: <de3ad953.0209200734.223b0533@posting.google.com> (raw)
In-Reply-To: xcvlm5xsu7r.fsf@hurricane.OCF.Berkeley.EDU
tfb@hurricane.OCF.Berkeley.EDU (Thomas F. Burdick) wrote in message news:<xcvlm5xsu7r.fsf@hurricane.OCF.Berkeley.EDU>...
> googleartist@yahoo.com (Artist) writes:
First of all thanks for such a good answer.
>
>
> I'm not positive I understand your question, but I think I do, and
> I've done this before: you want to use Emacs as a programming
> environment for making a somewhat-editor-like application that's not
> actually an editor, and you don't want your end users to need to know
> that it's Emacs underneath.
Yep, I would like to have it a reading application, where people can
search the stuff in big file in a variety of ways.
I also want to build a
>
> To do this, you want to build your own Emacs; You get the normal Emacs event loop, the mode
> line, minibuffer, and menu bar, but apart from that, you can control
> things to the extent that your users don't have to have any idea
> they're using Emacs[*].
The idea
If you're going to distribute this
> application (internal "distribution" in an organization doesn't
> count), you should look into the licensing issues, as I think it would
> fall under the GPL (whereas if you just used a standard Emacs as your
> environment, you could distribute your application seperately under
> whatever terms you wanted).
>
> [*] Of course, you should still credit Emacs somewhere, like an About
> box that says "this application is built on GNU Emacs" -- but you can
> control the application to the extent that your users won't need to
> realize this.
>
prev parent reply other threads:[~2002-09-20 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 13:59 Emacs as platform for the application Artist
2002-09-19 18:35 ` Thomas F. Burdick
2002-09-20 14:26 ` Kai Großjohann
2002-09-21 18:34 ` Thomas F. Burdick
2002-09-20 15:34 ` Artist [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:
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=de3ad953.0209200734.223b0533@posting.google.com \
--to=googleartist@yahoo.com \
/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).