From: Edgar A <edgar.factorial@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 25701@debbugs.gnu.org
Subject: bug#25701: 25.1; Fresh build on OS X doesn't get keyboard control after spawned
Date: Mon, 13 Feb 2017 00:07:13 -0800 [thread overview]
Message-ID: <5BA1E90A-07FB-4D21-BC91-315F7C9245E1@gmail.com> (raw)
In-Reply-To: <CAArVCkTiNeeXj-Lx1J4e5jKk+nCgNLRc+a7dyC8eNsh4ofB+Dw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Thank you for the reply.
But what about developing? I don’t necessarily want to install this on my machine, just to test/debug to fix an emacs bug.
> On Feb 13, 2017, at 12:05 AM, Philipp Stephani <p.stephani2@gmail.com> wrote:
>
>
>
> Edgar A <edgar.factorial@gmail.com <mailto:edgar.factorial@gmail.com>> schrieb am Mo., 13. Feb. 2017 um 08:39 Uhr:
> Hello,
>
> I'm on 862d6438cfa6c6c035033697751f3d002357b024 and built emacs with:
> `./configure --without-makeinfo`. This resulted in the binaries under
> `src` called `emacs` and `emacs-26.0.50.1`. Now when I start these
> binaries in a shell then the GUI does not end up getting the keyboard
> control and it continues typing in the shell. In addition, focus never
> shifts to the GUI and click on the top bar doesn't change focus to emacs
> although I'm able to move the GUI about.
>
> These binaries aren't proper application bundles in the macOS sense, so you can't run them directly. Run
> make install && open nextstep/Emacs.app
> instead.
[-- Attachment #2: Type: text/html, Size: 2060 bytes --]
next prev parent reply other threads:[~2017-02-13 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 5:38 bug#25701: 25.1; Fresh build on OS X doesn't get keyboard control after spawned Edgar A
2017-02-13 8:05 ` Philipp Stephani
2017-02-13 8:07 ` Edgar A [this message]
2017-02-13 8:10 ` Philipp Stephani
2017-02-18 17:51 ` npostavs
2017-02-18 18:57 ` Philipp Stephani
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=5BA1E90A-07FB-4D21-BC91-315F7C9245E1@gmail.com \
--to=edgar.factorial@gmail.com \
--cc=25701@debbugs.gnu.org \
--cc=p.stephani2@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 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).