Re: Emacs.app for OSX suggestions

[Xu Xin <railwaycat@gmail.com>]

On Fri, Feb 19, 2016 at 4:09 AM, Pavlos Vinieratos <pvinis@gmail.com> wrote:
> yes. i was wrong.
> like you said, runing emacs from the terminal, initiates every time.
> launching the app initiates once and connects every next time.
>
> so my real suggestion, is not to quit the app when i close the last window.
> would that make it so that when i click on the app again, it would open
> without initializing again? if yes, then thats my suggested change. if it
> would still initialize, then i would like that fixed.
>
> i might have to find how to test that myself, but is the initialization
> happening when the app launches, or when the first window is opened?
> by initialization i mean eval the init file. if it happens on app launch,
> then it should br easy to just keep the app running so when i click the app,
> even if its the first window (after i had the previous windows closed) would
> open quickly. but if the initialization happens on first window opening,
> then it might be a bit harder.
>
> thoughts?
>
> --
> 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
>>
>

Aquamacs has similar feature as you mentioned.

- Xin