From: Noam Postavsky <npostavs@gmail.com>
Date: Sat, 2 Jul 2016 01:15:28 +0000 (-0400)
Subject: Explain when package-initialize isn't called
X-Git-Tag: emacs-25.1-rc1~45
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=dec7567;p=emacs.git

Explain when package-initialize isn't called

* doc/lispref/os.texi (Startup Summary): Explain that package-initialize
is not called when options -q, -Q, or --batch were passed (Bug #19151).
---

diff --git a/doc/lispref/os.texi b/doc/lispref/os.texi
index 5f189b984a3..ec14b014e52 100644
--- a/doc/lispref/os.texi
+++ b/doc/lispref/os.texi
@@ -155,9 +155,13 @@ It loads your abbrevs from the file specified by
 option @samp{--batch} was specified.
 
 @item
-If @code{package-enable-at-startup} is non-@code{nil}, it calls the
-function @code{package-initialize} to activate any optional Emacs Lisp
-package that has been installed.  @xref{Packaging Basics}.
+It calls the function @code{package-initialize} to activate any
+optional Emacs Lisp package that has been installed.  @xref{Packaging
+Basics}.  However, Emacs doesn't initialize packages when
+@code{package-enable-at-startup} is @code{nil} or when it's started
+with one of the options @samp{-q}, @samp{-Q}, or @samp{--batch}.  To
+initialize packages in the latter case, @code{package-initialize}
+should be called explicitly (e.g., via the @samp{--funcall} option).
 
 @vindex after-init-time
 @item