unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Install C source code for for debugging help
Date: Sat, 28 Sep 2019 11:06:30 +0900	[thread overview]
Message-ID: <C7415393-FAB2-4F37-875B-77D44118AF26@traduction-libre.org> (raw)
In-Reply-To: <E1iE1bQ-0002sm-Rq@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]


> On Sep 28, 2019, at 10:32, 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. ]]]
> 
>> I expect that the overwhelming majority of the users don't want to see
>> the C source, but then, the vast majority of computer users use
>> proprietary software.
> 
>> I think Emacs should (and does) really make a special effort to go out
>> of its way to encourage users to access the source code.
> 
> I think it is enough to help users look at the source code
> once they decide to download it.
> 
> If you build and run Emacs uninstalled, this works automatically.  We
> could fairly easily make it more convenient for those who run
> installed Emacs and unpack the corresponding source in their home
> directories.
> 
> To go further than that would do no harm, but it could be a lot of
> work.  I suggest that people do the work if they want to.

As a non coder but curious user, I think the current setting is enough: checkout the code, build, check the source (either C or lisp), do your thing, build again, etc.

Most of the people who are interested in the entrails of free software, even if not for coding, are willing to take those extra steps, that are necessary anyway if they want to contribute at one point.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



[-- Attachment #2: Type: text/html, Size: 3435 bytes --]

  reply	other threads:[~2019-09-28  2:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 20:37 Install C source code for for debugging help Paul Eggert
2019-09-27  5:07 ` Eli Zaretskii
2019-09-27  6:13   ` Paul Eggert
2019-09-27  7:19     ` Eli Zaretskii
2019-09-27 13:01       ` Stefan Monnier
2019-09-27 13:12         ` Stefan Monnier
2019-09-27 13:33         ` Eli Zaretskii
2019-09-27 13:48           ` Stefan Monnier
2019-09-27 13:56             ` Eli Zaretskii
2019-09-27 14:24               ` Paul Eggert
2019-09-27 14:40                 ` Eli Zaretskii
2019-09-28  4:03                   ` Paul Eggert
2019-09-27 17:04                 ` Noam Postavsky
2019-09-27 22:45                   ` Fu Yuan
2019-09-28  0:09                     ` Juanma Barranquero
2019-09-28  2:14                     ` Michael Rohleder
2019-09-27 15:25               ` Stefan Monnier
2019-09-28  1:32                 ` Richard Stallman
2019-09-28  2:06                   ` Jean-Christophe Helary [this message]
2019-09-27 15:03             ` Lars Ingebrigtsen
2019-09-27 15:47             ` David Ringo
2019-09-27  8:37     ` Andreas Schwab
2019-09-27  9:06       ` Eli Zaretskii
2019-09-27 11:58         ` Andreas Schwab
2019-09-27 12:58           ` Eli Zaretskii
2019-09-27 13:45             ` Andreas Schwab
2019-09-27 13:50               ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28 18:19 Angelo Graziosi
2019-09-29  6:56 ` Paul Eggert

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=C7415393-FAB2-4F37-875B-77D44118AF26@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).