ok. so right now, the app just starts 'emacs'. so no mattet what, it makes
a new instance and always evals the init file, disregarding any existing
daemon or already running instance.
what im suggesting, is that it starts 'emacsclient', possibly with '-a ""',
so if there is an already running daemon, it connects to that instance, so
the initialization doesnt need to happen again.
does it make sense?

-- 
Pavlos Vinieratos

On 18 February 2016 at 10:54:20, pavlos vinieratos (pvinis@gmail.com) wrote:

> Hello. The way Emacs.app works right now, it that it always starts a new
> session of emacs, so its always slow to open if you have more than an empty
> init file, and it doesn’t work with the daemon.
>
> I would suggest to change the behaviour of that, and make it so that
> Emacs.app will start emacsclient, so if a daemon is running, it would
> connect to it. We could even make it so that it starts a new daemon like
> `-a “”` would.
>
> I think that would benefit anyone using Emacs.app by doing what those same
> people would do now, which is to run a command from their shell, that does
> the above. Why not implement it in the .app, so that when dragging some
> files onto Emacs.app, it starts quickly because of the daemon?
>
>
>
> --
> Pavlos Vinieratos
>
>