all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: missing src/ directory for eval.c
Date: Mon, 11 Feb 2019 17:44:33 +0100	[thread overview]
Message-ID: <20190211164432.GC9674@tuxteam.de> (raw)
In-Reply-To: <87d0ny5p9y.fsf@gmx.de>

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

On Mon, Feb 11, 2019 at 04:16:25PM +0100, Michael Albinus wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 
> Hi Stefan,
> 
> > Part of the idea is that, if you're not compiling Emacs yourself,
> > accessing the C source code is much less useful.
> 
> Like for every general rule, there are counter examples. I, for example,
> cannot build Emacs under MS Windows, I'm bound to
> distributions. Nevertheless, I could use the C sources when debugging
> there, in order to read them.

I concur: one of Emacs's strong points is that it readily gives you
easy access to its innards (the "study" part in the four freedoms,
after all :-)

Cheers
-- t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2019-02-11 16:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 11:35 missing src/ directory for eval.c (Was: 1L?) Van Ly
2019-02-11 13:03 ` tomas
2019-02-11 13:56   ` Noam Postavsky
2019-02-11 14:13 ` missing src/ directory for eval.c Stefan Monnier
2019-02-11 15:16   ` Michael Albinus
2019-02-11 16:44     ` tomas [this message]
2019-02-11 20:51   ` Robert Thorpe
2019-02-11 20:54     ` Emanuel Berg
2019-02-11 22:11     ` Stefan Monnier
2019-02-12  0:01       ` Emanuel Berg
2019-02-12  4:00         ` Stefan Monnier
2019-02-12  5:16           ` Emanuel Berg
2019-02-11 14:17 ` missing src/ directory for eval.c (Was: 1L?) Yuri Khan
2019-02-11 20:45   ` Emanuel Berg
2019-02-11 22:01   ` Van L
2019-02-12  0:04     ` Emanuel Berg
2019-02-12 12:21       ` missing src/ directory for eval.c Van L

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=20190211164432.GC9674@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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.