Why can't OSX handle Emacs client frames

Why can't OSX handle Emacs client frames

[Ben Mezger]

By using the latest Emacs version from [1], it seems that when running
in daemon-mode and when opening a new client frame from the terminal
or from a custom OSX app I wrote which opens a new frame when clicking
or starts a new daemon is case it's not running, it seems I am unable
to ⌘-tab.

The only way for me to find the client frame, is by running Mission
Control with the touchpad or by moving the client to a full-screen
desktop and then swiping to that desktop Although the Emacs client is
running, I am also unable to see the client Emacs dock icon of a
running client.

Any reason why this happens and why can't I manage these frames with
OSX? Really annoying not being able to ⌘-tab or by clicking the emacs
icon in doc.

[1] - https://emacsformacosx.com/

-- 
Kind regards,
Met een vriendelijke groet,

Ben Mezger
https://seds.nl
PGP: B456 B356 E3DC F1A6 1479  C936 AC7A 3084 3ADC 0D65

Re: Why can't OSX handle Emacs client frames

[Doug Davis]

A potentially unsatisfactory suggestion: one can cycle through
individual windows of an application using Command + ` (back quote) on
macOS.

I personally use a fresh build of the master branch on macOS (and use
the above suggestion), but if you're not already aware of it, you might
be interested in Mitsuharu Yamamoto's emacs-mac port [1] (which can also
be installed via Homebrew [2]). It supports a lot of macOS specific
features. It might do a better job of handling client frames, I'm not
sure though. The README does mention keyboard shortcut improvements [3].

    drd

[1] https://bitbucket.org/mituharu/emacs-mac/src/master/
[2] https://github.com/railwaycat/homebrew-emacsmacport
[3] https://bitbucket.org/mituharu/emacs-mac/src/3bf213d502a8260d29f7f55eb0938fc0a2594ea2/README-mac#lines-167:168