all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: emacs-devel@gnu.org
Subject: Re: lldb support
Date: Thu, 10 Nov 2016 20:46:50 -0800	[thread overview]
Message-ID: <87vavulj2d.fsf@vostro.rath.org> (raw)
In-Reply-To: <E1c50bi-0003OQ-6b@fencepost.gnu.org> (Richard Stallman's message of "Thu, 10 Nov 2016 20:26:18 -0500")

On Nov 10 2016, Richard Stallman <rms@gnu.org> wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > > Why would we want to support it
>   > > rather than saying, "We support GDB -- use that."?
>
>   > All the usual reasons people prefer tool A over tool B: compatibility 
>   > with a specific environment, personal customizations, familiarity, and 
>   > personal preference. LLDB is free software. We should support it.
>
> Your argument disregards the important fact that LLDB is part
> of a project that aims to replace many important GNU packages,
> and its success is the GNU Project's loss.
>
> I think that that is not important to you, but it is very
> important for the GNU Project.

Doesn't the same apply to the Linux kernel, whose success is the GNU
(Hurd) Project's loss? Yet Emacs seems to support Linux even better than
it supports Hurd.

(Just curious).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«



  parent reply	other threads:[~2016-11-11  4:46 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 [this message]
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
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=87vavulj2d.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=emacs-devel@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.