From: John Wiegley <jwiegley@gmail.com>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: Daniel Colascione <dancol@dancol.org>,
Emacs developers <emacs-devel@gnu.org>,
rms@gnu.org, "Perry E. Metzger" <perry@piermont.com>
Subject: Re: lldb support
Date: Fri, 11 Nov 2016 09:47:18 -0800 [thread overview]
Message-ID: <m24m3d52op.fsf@newartisans.com> (raw)
In-Reply-To: <CAGK7Mr5Hietnh09X9igsg8D0VfviFZU8V_5g9NX87Twb+TQyMg@mail.gmail.com> (Philippe Vaucher's message of "Fri, 11 Nov 2016 10:44:32 +0100")
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
>>>>> "PV" == Philippe Vaucher <philippe.vaucher@gmail.com> writes:
VP> If people find the alternative better it should be intencive to improve
PV> the GNU packages... not to try to find ways of preventing them to use the
PV> alternative (which is the wrong answer in my honest opinion, it's a sort
PV> of vendor lockin).
[...]
PV> I don't think that promoting the GNU project should be more important than
VP> having Emacs support free software, especially for something most Emacs
VP> user would expect it to do.
I strongly agree. Inhibiting users' freedom to choose other *free* software,
because that other free software is not part of the GNU project, makes it
sound like the ubiquity of the GNU project, and not user freedom, is the goal.
I understand believing that "GNU everywhere" could increase freedom due to the
nature of the GPL, but now it starts to sound a lot more like "freedom to use
what the FSF thinks you should use", rather than real freedom -- especially
when the FSF's choices are less capable than other free alternatives.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-11-11 17:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 20:05 lldb support Perry E. Metzger
2016-11-07 20:20 ` Stefan Monnier
2016-11-08 3:08 ` Perry E. Metzger
2016-11-08 13:19 ` Stefan Monnier
2016-11-08 19:58 ` John Wiegley
2016-11-09 0:54 ` Richard Stallman
2016-11-09 1:17 ` Daniel Colascione
2016-11-09 3:42 ` Eli Zaretskii
2016-11-10 0:24 ` Richard Stallman
2016-11-10 0:26 ` Daniel Colascione
2016-11-11 1:26 ` Richard Stallman
2016-11-11 4:24 ` Stefan Monnier
2016-11-11 4:46 ` Nikolaus Rath
2016-11-12 0:42 ` Richard Stallman
2016-11-11 9:44 ` Philippe Vaucher
2016-11-11 17:11 ` Stefan Monnier
2016-11-11 17:42 ` Stefan Huchler
2016-11-11 17:47 ` John Wiegley [this message]
2016-11-12 0:59 ` Stefan Huchler
2016-11-12 22:30 ` Richard Stallman
2016-11-14 21:58 ` John Wiegley
2016-11-16 4:13 ` Joseph Mingrone
2016-11-16 14:27 ` Stefan Monnier
2016-12-25 20:43 ` Richard Stallman
2016-11-11 19:01 ` Sam Steingold
2016-11-12 1:02 ` Stefan Huchler
2016-11-12 22:25 ` Richard Stallman
2016-11-12 0:54 ` Perry E. Metzger
2016-11-12 22:30 ` Richard Stallman
2016-11-10 1:51 ` Perry E. Metzger
2016-11-10 1:57 ` Perry E. Metzger
2016-11-10 3:43 ` Eli Zaretskii
2016-11-10 9:33 ` Toon Claes
2016-11-10 15:57 ` Eli Zaretskii
2016-11-10 16:27 ` Toon Claes
2016-11-10 17:19 ` Eli Zaretskii
2016-11-12 7:04 ` Toon Claes
2016-11-12 7:47 ` Eli Zaretskii
2017-01-04 21:35 ` Toon Claes
2016-11-10 13:58 ` Perry E. Metzger
2016-11-10 16:02 ` Eli Zaretskii
2016-11-09 1:37 ` John Wiegley
2016-11-09 3:06 ` Perry E. Metzger
2016-11-10 0:23 ` Richard Stallman
2016-11-10 1:18 ` John Mastro
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=m24m3d52op.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
--cc=philippe.vaucher@gmail.com \
--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.