all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Søren Pilgård" <fiskomaten@gmail.com>
To: Ivan Kanis <banana@kanis.fr>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: develop an emacs library
Date: Mon, 18 Mar 2013 00:17:12 +0100	[thread overview]
Message-ID: <CAGXii2Y+OyFPft=rvECXMB8kVwQot5ct4oS53D5b2T=godN3tg@mail.gmail.com> (raw)
In-Reply-To: <878v5ma5ta.fsf@kanis.fr>

On Sun, Mar 17, 2013 at 7:39 AM, Ivan Kanis <banana@kanis.fr> wrote:
> March, 16 at 20:02 Richard wrote:
>
>>     Why do you think a commercial company would use a elisp library?
>>
>> To make a nonfree extended version of Emacs, perhaps.
>
> Emacs users are a minority. At my company we are less than 5%. I think
> you are worrying for things that won't happen. Anyway it was just an
> idea that I don't have time to implement so you needn't worry.
>

I think the fear here is for situations like this:
Some small company sees how popular new editors like lighttable and
sublimetext is. Wanting to cash in on this easily they make a shiny
interface relying on this "emacs library" for doing the base work.

GPL ensures people don't just download the source code and do this,
but it is unclear whether providing this "emacs library" could open a
way to circumvent this.



      reply	other threads:[~2013-03-17 23:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 19:01 develop an emacs library Ivan Kanis
2013-03-14 19:35 ` Jambunathan K
2013-03-14 20:19 ` joakim
2013-03-15  4:23   ` develop an emacs library, " Ivan Kanis
2013-03-15  4:31     ` Jay Belanger
2013-03-15 20:07       ` Ivan Kanis
2013-03-14 22:30 ` Richard Stallman
2013-03-15 20:18   ` Ivan Kanis
2013-03-17  0:02     ` Richard Stallman
2013-03-17  6:39       ` Ivan Kanis
2013-03-17 23:17         ` Søren Pilgård [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

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

  git send-email \
    --in-reply-to='CAGXii2Y+OyFPft=rvECXMB8kVwQot5ct4oS53D5b2T=godN3tg@mail.gmail.com' \
    --to=fiskomaten@gmail.com \
    --cc=banana@kanis.fr \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.