From: Itai Berli <itai.berli@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Emacs developers <emacs-devel@gnu.org>,
Tino Calancha <tino.calancha@gmail.com>
Subject: Re: Help getting started debugging Emacs on macOS Sierra
Date: Sat, 12 Aug 2017 15:08:53 +0300 [thread overview]
Message-ID: <CABsNJ=NtkYA6hX5zOJC8voFRrPME5b9VvyHEZq84+pPj699v+Q@mail.gmail.com> (raw)
In-Reply-To: <874ltduhdg.fsf@rosalinde>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Thanks, everyone. What's the difference between emacs and bootstrap-emacs?
On Sat, Aug 12, 2017 at 2:59 PM, Stephen Berman <stephen.berman@gmx.net>
wrote:
> On Sat, 12 Aug 2017 20:43:58 +0900 (JST) Tino Calancha <
> tino.calancha@gmail.com> wrote:
>
> > On Sat, 12 Aug 2017, Itai Berli wrote:
> >
> >> Thanks. A new executable appeared in the src folder: emacs-26.0.50.2Is
> this
> >> the executable that I need to run to see the changes
> >> I made?
> > Yes, that one.
> >> Generally speaking, whenever I make a change and rebuild, do I need to
> >> change the target file that I run (emacs-26.0.50.2, .3,
> >> .4, etc.)?
> > Yes, if you don't have bootstrap-emacs.
> > In my sistem running GNU/Linux, everytime i rebuild i get: *)
> emacs-26.0.50.N
> > (N=1,2,3, ...)
> > *) i also get the file bootstrap-emacs; this file is overwritten after
> > every compilation. I always chose bootstrap-emacs as the executable
> to
> > compile.
>
> IIUC, on GNU/Linux bootstrap-emacs is a hard link to the latest
> executable, and there should also be another hard link called simply
> emacs; that's what I execute when I want the most recent built
> executable. I don't know if other platforms also have this setup.
>
> Steve Berman
>
[-- Attachment #2: Type: text/html, Size: 1781 bytes --]
next prev parent reply other threads:[~2017-08-12 12:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:25 Help getting started debugging Emacs on macOS Sierra Itai Berli
2017-08-11 3:04 ` Paul Eggert
2017-08-11 5:06 ` Itai Berli
2017-08-11 8:47 ` Paul Eggert
2017-08-11 8:57 ` Itai Berli
2017-08-11 9:27 ` Itai Berli
2017-08-11 9:52 ` Eli Zaretskii
2017-08-11 9:55 ` Itai Berli
2017-08-11 9:59 ` Itai Berli
2017-08-11 10:09 ` Itai Berli
2017-08-11 11:46 ` Tino Calancha
2017-08-11 12:14 ` Itai Berli
2017-08-11 12:33 ` Tino Calancha
2017-08-11 12:40 ` Itai Berli
2017-08-11 12:48 ` Tino Calancha
2017-08-11 13:17 ` Itai Berli
2017-08-11 13:20 ` Tino Calancha
2017-08-11 13:25 ` Itai Berli
2017-08-11 14:18 ` Eli Zaretskii
2017-08-11 14:42 ` Itai Berli
2017-08-11 15:08 ` Eli Zaretskii
2017-08-11 15:34 ` Itai Berli
2017-08-11 16:07 ` Itai Berli
2017-08-11 16:08 ` Eli Zaretskii
2017-08-11 17:32 ` Itai Berli
2017-08-12 9:53 ` Itai Berli
2017-08-12 10:20 ` Eli Zaretskii
2017-08-12 10:43 ` Itai Berli
2017-08-12 11:43 ` Tino Calancha
2017-08-12 11:59 ` Stephen Berman
2017-08-12 12:08 ` Itai Berli [this message]
2017-08-12 12:14 ` Stephen Berman
2017-08-12 12:15 ` Eli Zaretskii
2017-08-12 13:28 ` Itai Berli
2017-08-12 13:47 ` Tino Calancha
2017-08-12 14:20 ` Anders Lindgren
2017-08-12 11:57 ` Eli Zaretskii
2017-08-11 12:43 ` Eli Zaretskii
2017-08-11 9:35 ` Eli Zaretskii
2017-08-11 6:28 ` Eli Zaretskii
2017-08-11 8:27 ` Itai Berli
2017-08-11 9:30 ` Eli Zaretskii
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='CABsNJ=NtkYA6hX5zOJC8voFRrPME5b9VvyHEZq84+pPj699v+Q@mail.gmail.com' \
--to=itai.berli@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
--cc=tino.calancha@gmail.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.