* Should `server-force-delete' also stop the server process?
@ 2010-08-09 16:31 Leo
2010-08-09 17:11 ` Juanma Barranquero
0 siblings, 1 reply; 5+ messages in thread
From: Leo @ 2010-08-09 16:31 UTC (permalink / raw)
To: emacs-devel
Hello,
When running the server through tcp and run server-force-delete, only
the server-file is deleted, the network process continue to listen on
a tcp port. I wonder if this is the intended behaviour.
Thanks.
Leo
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should `server-force-delete' also stop the server process?
2010-08-09 16:31 Should `server-force-delete' also stop the server process? Leo
@ 2010-08-09 17:11 ` Juanma Barranquero
2010-08-09 17:22 ` Leo
0 siblings, 1 reply; 5+ messages in thread
From: Juanma Barranquero @ 2010-08-09 17:11 UTC (permalink / raw)
To: Leo; +Cc: emacs-devel
> When running the server through tcp and run server-force-delete, only
> the server-file is deleted, the network process continue to listen on
> a tcp port. I wonder if this is the intended behaviour.
The docstring says:
server-force-delete is an interactive compiled Lisp function in `server.el'.
(server-force-delete &optional NAME)
Unconditionally delete connection file for server NAME.
If server is running, it is first stopped.
NAME defaults to `server-name'. With argument, ask for NAME.
so it should stop the process. Do you have a recipe where it doesn't?
(If so, please file a bug report.)
Juanma
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should `server-force-delete' also stop the server process?
2010-08-09 17:11 ` Juanma Barranquero
@ 2010-08-09 17:22 ` Leo
2010-08-09 17:25 ` Leo
0 siblings, 1 reply; 5+ messages in thread
From: Leo @ 2010-08-09 17:22 UTC (permalink / raw)
To: emacs-devel
On 2010-08-09 18:11 +0100, Juanma Barranquero wrote:
> so it should stop the process. Do you have a recipe where it doesn't?
> (If so, please file a bug report.)
Reported as http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6832.
Thanks.
Leo
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should `server-force-delete' also stop the server process?
2010-08-09 17:22 ` Leo
@ 2010-08-09 17:25 ` Leo
2010-08-09 18:28 ` Juanma Barranquero
0 siblings, 1 reply; 5+ messages in thread
From: Leo @ 2010-08-09 17:25 UTC (permalink / raw)
To: emacs-devel
On 2010-08-09 18:22 +0100, Leo wrote:
> On 2010-08-09 18:11 +0100, Juanma Barranquero wrote:
>> so it should stop the process. Do you have a recipe where it doesn't?
>> (If so, please file a bug report.)
>
> Reported as http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6832.
>
> Thanks.
> Leo
BTW, why not use a name like `server-stop' vs `server-start'? I have
found myself trying M-x server-stop before remembering it is
server-force-delete.
Leo
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should `server-force-delete' also stop the server process?
2010-08-09 17:25 ` Leo
@ 2010-08-09 18:28 ` Juanma Barranquero
0 siblings, 0 replies; 5+ messages in thread
From: Juanma Barranquero @ 2010-08-09 18:28 UTC (permalink / raw)
To: Leo; +Cc: emacs-devel
On Mon, Aug 9, 2010 at 19:25, Leo <sdl.web@gmail.com> wrote:
> BTW, why not use a name like `server-stop' vs `server-start'?
(server-start t) ; t == LEAVE-DEAD
or
(server-mode -1)
should suffice.
> I have
> found myself trying M-x server-stop before remembering it is
> server-force-delete.
server-force-delete is not server-stop. Read the docstrings for it and
server-start.
Juanma
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-08-09 18:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-09 16:31 Should `server-force-delete' also stop the server process? Leo
2010-08-09 17:11 ` Juanma Barranquero
2010-08-09 17:22 ` Leo
2010-08-09 17:25 ` Leo
2010-08-09 18:28 ` Juanma Barranquero
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).