me/guix
Archived
1
0
Fork 0
Code Activity

doc: Update to reflect the current installation prefix of Emacs packages.

Browse source 
* doc/guix.texi (Application Setup)[Emacs Packages]: No longer mention the
guix.d Elisp installation prefix.  Do not treat the user profile specially, as
it is not special anymore.
(Build Systems): Document the correct Elisp installation prefix.
This commit is contained in:
Maxim Cournoyer 2020-03-01 23:04:00 -05:00
parent d5195020d2
commit fdffceeb01
No known key found for this signature in database
GPG key ID: 1260E46482E63562
1 changed files with 13 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
doc/guix.texi
View file

@ -1738,22 +1738,18 @@ information.
@subsection Emacs Packages @subsection Emacs Packages
@cindex @code{emacs} @cindex @code{emacs}
When you install Emacs packages with Guix, the elisp files may be placed When you install Emacs packages with Guix, the Elisp files are placed
either in @file{$HOME/.guix-profile/share/emacs/site-lisp/} or in under the @file{share/emacs/site-lisp/} directory of the profile in
sub-directories of which they are installed. The Elisp libraries are made available to
@file{$HOME/.guix-profile/share/emacs/site-lisp/guix.d/}. The latter Emacs through the @code{EMACSLOADPATH} environment variable, which is
directory exists because potentially there may exist thousands of Emacs set when installing Emacs itself.
packages and storing all their files in a single directory may not be
reliable (because of name conflicts). So we think using a separate
directory for each package is a good idea. It is very similar to how
the Emacs package system organizes the file structure (@pxref{Package
Files,,, emacs, The GNU Emacs Manual}).
By default, Emacs (installed with Guix) ``knows'' where these packages Additionally, autoload definitions are automatically evaluated at the
are placed, so you do not need to perform any configuration. If, for initialization of Emacs, by the Guix-specific
some reason, you want to avoid auto-loading Emacs packages installed @code{guix-emacs-autoload-packages} procedure. If, for some reason, you
with Guix, you can do so by running Emacs with @code{--no-site-file} want to avoid auto-loading the Emacs packages installed with Guix, you
option (@pxref{Init File,,, emacs, The GNU Emacs Manual}). can do so by running Emacs with the @code{--no-site-file} option
(@pxref{Init File,,, emacs, The GNU Emacs Manual}).
@subsection The GCC toolchain @subsection The GCC toolchain
@ -6681,9 +6677,8 @@ of Emacs itself (@pxref{Packages,,, emacs, The GNU Emacs Manual}).
It first creates the @code{@code{package}-autoloads.el} file, then it It first creates the @code{@code{package}-autoloads.el} file, then it
byte compiles all Emacs Lisp files. Differently from the Emacs byte compiles all Emacs Lisp files. Differently from the Emacs
packaging system, the Info documentation files are moved to the standard packaging system, the Info documentation files are moved to the standard
documentation directory and the @file{dir} file is deleted. Each documentation directory and the @file{dir} file is deleted. The Elisp
package is installed in its own directory under package files are installed directly under @file{share/emacs/site-lisp}.
@file{share/emacs/site-lisp/guix.d}.
@end defvr @end defvr
@defvr {Scheme Variable} font-build-system @defvr {Scheme Variable} font-build-system