unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Valente <johnv02139@yahoo.com>,
	hector <hectorlahoz@gmail.com>,
	help-gnu-emacs@gnu.org
Subject: RE: debugging Emacs LISP functions
Date: Wed, 1 Mar 2017 10:31:33 -0800 (PST)	[thread overview]
Message-ID: <6203cb70-5410-4ab6-9a69-706a7b2c99ff@default> (raw)
In-Reply-To: <1134748621.1292569.1488389611565@mail.yahoo.com>

> The blurring between "user" and "developer", in this case, has nothing
> to do with free software.

Not sure just what you meant by "in this case".  But the distinction
between user and developer _does_, in general, have something to do
with _free software_.  It has at least these two, essentially
independent, things to do with free software:

1. Users can be developers of the Emacs product that is distributed
   ("core" Emacs).  A "developer" role here is pretty much open to
   any user (and even non-users).

2. Free software means freely available source code.  And with the
   GPL, anyone is permitted to use, copy, and modify copies of the
   source code, within the rights of the license.

Non-free software typically does not allow for either of these.
It can sometimes allow for #1 (development by users) to some extent.
But ource code (at least some of it) is typically not made available
to everyone who uses non-free software.

There is another sense in which _Emacs_ is a bit special wrt the
user/developer distinction: its _ease_ of
customization/modification/development by users.  Emacs has
always had user modification and ease of that as one of its
primary features.  It is a poster child for this.



      reply	other threads:[~2017-03-01 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 12:14 debugging Emacs LISP functions hector
2017-03-01 12:30 ` chaouche yacine
2017-03-01 14:01 ` Stefan Monnier
2017-03-01 17:33 ` John Valente
2017-03-01 18:31   ` Drew Adams [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=6203cb70-5410-4ab6-9a69-706a7b2c99ff@default \
    --to=drew.adams@oracle.com \
    --cc=hectorlahoz@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=johnv02139@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).