From: Glenn Morris <rgm@gnu.org>
To: Emilio Lopes <eclig@gmx.net>
Cc: 18487@debbugs.gnu.org
Subject: bug#18487: `server-running-p' not autoloaded
Date: Wed, 17 Sep 2014 15:43:15 -0400 [thread overview]
Message-ID: <xir3zavxrg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CANiPZaAL5SNLk1bN56ch81wkUoH2cQ+Ooyvx2geNz1kuQrEnGA@mail.gmail.com> (Emilio Lopes's message of "Tue, 16 Sep 2014 22:11:21 +0200")
Emilio Lopes wrote:
> The function `server-running-p' is not autoloaded. That means that
> the following code in
> the user's init-file will result in an error:
>
> (unless (or noninteractive
> (server-running-p))
> (server-start))
Since it's not interactive, why does it matter?
Ie, just stick a (require 'server) in there.
prev parent reply other threads:[~2014-09-17 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:11 bug#18487: `server-running-p' not autoloaded Emilio Lopes
2014-09-17 19:43 ` Glenn Morris [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xir3zavxrg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=18487@debbugs.gnu.org \
--cc=eclig@gmx.net \
/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 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).