From b1d2cf2c2ca86151c25d1c59c7eb210179086be2 Mon Sep 17 00:00:00 2001 From: Noam Postavsky Date: Fri, 1 Jul 2016 21:15:28 -0400 Subject: [PATCH v2] 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). --- doc/lispref/os.texi | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/lispref/os.texi b/doc/lispref/os.texi index 5f189b9..ec14b01 100644 --- a/doc/lispref/os.texi +++ b/doc/lispref/os.texi @@ -155,9 +155,13 @@ Startup Summary 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 -- 2.8.0