[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: point of "buffer still has clients" message

From: Jarek Czekalski
Subject: Re: point of "buffer still has clients" message
Date: Wed, 27 Nov 2013 08:32:14 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0

W dniu 2013-11-26 16:55, Barry Margolin pisze:
When you have EDITOR set to most editors, the client starts a new editor
process, you edit the file, save it, and then exit the editor. The
client waits for the editor to exit, then it will use the result.

But when you use emacsclient, it's not so simple. Emacs keeps on running
after you save the file. Emacsclient is waiting for a message from emacs
telling it that it you're done, so it should exit, and then its client
application can use the result. You do this with the server-edit (C-x #)

Barry, that definitely helps to understand the idea. But still it's not clear why the things done in server-edit command couldn't be done during kill-buffer. The user request is "close the file". They shouldn't have to choose between server-edit and kill-buffer.

The user experience is as follows:
1. a shortcut is bound to kill-this-buffer
2. a buffer is edited throught emacsclient
3. user wants to kill the buffer with the shortcut he always uses for that or using "File / Close" menu option

So far you both didn't give any justification for the confirmation message. If things stay this way we should assume that this message is unnecessary and should be removed.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]