Re: Question about Emacs client and server

[PierGianLuca <luca@magnaspesmeretrix.org>]

Thank you very much, Eric!

It work almost smoothly. But it still has some "glitches" (with respect to my workflow).

For example, if I issue a "kill-current-buffer" in a "client buffer" (no "@"), then the buffer will be killed, but the frame stays there, displaying some other buffer (which is what I want). If the frame displayed two buffers, the other buffer remains.

If I issue a "kill-current-buffer" in a "client buffer" (showing "@"), then the whole frame is also closed. This is slightly annoying because I have to check whether the "@" is there or not, in order to know whether the frame will be deleted or not.

On 230712 14:34, Eric S Fraga wrote:
> I achieve pretty much what you want by *always* executing
> 
> emacsclient -a emacs -c
> 
> (with optional file to open) which will start a fresh emacs is not
> already running but otherwise will create a new frame.
> 
> It is up to your emacs initialization to take care of the desktop
> configuration (something I do not do).
> 
> The only thing I cannot help with is:
> 
>> I notice that some Emacs frames are "emacsclient" ones (they have a
>> "@" in the status line); others are not. I don't see why they should
>> be different.
> 
> but I don't find this to be an issue.  YMMV, of course.
>