Commit dec75675 authored by Noam Postavsky's avatar Noam Postavsky
Browse files

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).
parent 113d1e2b
......@@ -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
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment