all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Argument leave-dead to emacs-start is not explained in doc string
Date: Sat, 27 Jan 2007 19:47:27 +0100	[thread overview]
Message-ID: <86tzyc9uio.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <ur6tg9wg7.fsf@gnu.org> (Eli Zaretskii's message of "Sat\, 27 Jan 2007 20\:05\:44 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Tue, 23 Jan 2007 16:37:29 +0100
>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
>> 
>> Just that.
>
> What is emacs-start, and where is it defined?
>
> (Really, Lennart, you, of all the people, should have known how to
> make a proper bug report!)

M-x apropos-documentation RET leave-dead RET

server-start
  Command: Allow this Emacs process to be a server for client processes.
This starts a server communications subprocess through which
client "editors" can send your editing commands to this Emacs job.
To use the server, set up the program `emacsclient' in the
Emacs distribution as your standard "editor".

Prefix arg means just kill any existing server communications subprocess.

(fn &optional LEAVE-DEAD)


It is somewhat amusing that the function is called "server-start"
rather than "emacs-start" and that the meaning of a prefix argument is
explained in the DOC string.

Let is just assume that Lennart wanted to pretest our abilities to
deal with unfathomable bug reports.

-- 
David Kastrup

  reply	other threads:[~2007-01-27 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 15:37 Argument leave-dead to emacs-start is not explained in doc string Lennart Borgman (gmail)
2007-01-27 18:05 ` Eli Zaretskii
2007-01-27 18:47   ` David Kastrup [this message]
2007-01-27 19:05     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86tzyc9uio.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.