From: tomas@tuxteam.de
To: Van Ly <vy0123@me.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: missing src/ directory for eval.c (Was: 1L?)
Date: Mon, 11 Feb 2019 14:03:46 +0100 [thread overview]
Message-ID: <20190211130346.GA32312@tuxteam.de> (raw)
In-Reply-To: <3EAFCC26-4B10-4133-9B5E-C0BE117A5455@me.com>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Mon, Feb 11, 2019 at 10:35:45PM +1100, Van Ly wrote:
> > If I were you, I'd file a bug report with NetBSD.
[...]
> With more experience packaging and distributing GNU/Emacs, I want to believe the packages for masses by maintaners are better than what I can roll my own. It may not "just work" for you and me if we move the git-repo after `make install`.
Can't confirm: I always compile Emacs off git and "make install".
Source dir is always in the right place for C-x C-f to find the C
sources. I strongly suspect the packaging to be at fault in this.
Cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-02-11 13:03 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 [this message]
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
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=20190211130346.GA32312@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=vy0123@me.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.
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.