From 1a3e6b15badbd227516c7527e8cdb6095a39031b Mon Sep 17 00:00:00 2001 From: Alex Kost Date: Fri, 1 Jul 2016 11:12:33 +0300 Subject: doc: Describe how to make X server find TrueType fonts. * doc/guix.texi (Application Setup): Document how to add TrueType fonts installed in a Guix profile to the X server font path. --- doc/guix.texi | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'doc/guix.texi') diff --git a/doc/guix.texi b/doc/guix.texi index 393efab6e4..9703c72ff5 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -13,6 +13,7 @@ Copyright @copyright{} 2012, 2013, 2014, 2015, 2016 Ludovic Courtès@* Copyright @copyright{} 2013, 2014, 2016 Andreas Enge@* Copyright @copyright{} 2013 Nikita Karetnikov@* +Copyright @copyright{} 2014, 2015, 2016 Alex Kost@* Copyright @copyright{} 2015, 2016 Mathieu Lirzin@* Copyright @copyright{} 2014 Pierre-Antoine Rault@* Copyright @copyright{} 2015 Taylan Ulrich Bayırlı/Kammer@* @@ -1208,6 +1209,24 @@ for Chinese languages: guix package -i font-adobe-source-han-sans:cn @end example +Older programs such as @command{xterm} do not use Fontconfig and instead +rely on server-side font rendering. Such programs require to specify a +full name of a font using XLFD (X Logical Font Description), like this: + +@example +-*-dejavu sans-medium-r-normal-*-*-100-*-*-*-*-*-1 +@end example + +To be able to use such full names for the TrueType fonts installed in +your Guix profile, you need to extend the font path of the X server: + +@example +xset +fp ~/.guix-profile/share/fonts/truetype +@end example + +After that, you can run @code{xlsfonts} (from @code{xlsfonts} package) +to make sure your TrueType fonts are listed there. + @subsection X.509 Certificates The @code{nss-certs} package provides X.509 certificates, which allow -- cgit 1.4.1 From 424a323e92d92284efcd30cf548d1f41c556d592 Mon Sep 17 00:00:00 2001 From: myglc2 Date: Thu, 21 Jul 2016 18:35:34 -0400 Subject: doc: Explain when guix edit is read-only. * doc/guix.texi (Invoking guix edit): Explain when you can and can't edit the recipe. Signed-off-by: Alex Kost --- doc/guix.texi | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'doc/guix.texi') diff --git a/doc/guix.texi b/doc/guix.texi index 9703c72ff5..ec22d94a9a 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -4536,8 +4536,9 @@ You can freely access a huge library of build logs! @cindex package definition, editing So many packages, so many source files! The @command{guix edit} command -facilitates the life of packagers by pointing their editor at the source -file containing the definition of the specified packages. For instance: +facilitates the life of users and packagers by pointing their editor at +the source file containing the definition of the specified packages. +For instance: @example guix edit gcc@@4.9 vim @@ -4545,9 +4546,15 @@ guix edit gcc@@4.9 vim @noindent launches the program specified in the @code{VISUAL} or in the -@code{EDITOR} environment variable to edit the recipe of GCC@tie{}4.9.3 +@code{EDITOR} environment variable to view the recipe of GCC@tie{}4.9.3 and that of Vim. +If you are using a Guix Git checkout (@pxref{Building from Git}), or +have created your own packages on @code{GUIX_PACKAGE_PATH} +(@pxref{Defining Packages}), you will be able to edit the package +recipes. Otherwise, you will be able to examine the read-only recipes +for packages currently in the store. + If you are using Emacs, note that the Emacs user interface provides the @kbd{M-x guix-edit} command and a similar functionality in the ``package info'' and ``package list'' buffers created by the @kbd{M-x -- cgit 1.4.1