# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/elisp-common.eclass,v 1.17 2007/04/18 10:45:44 opfer Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/elisp-common.eclass,v 1.18 2007/04/19 13:26:37 ulm Exp $
#
# Copyright 2007 Christian Faulhammer <opfer@gentoo.org>
# Copyright 2002-2007 Matthew Kennedy <mkennedy@gentoo.org>
# USAGE:
#
# Usually you want to use this eclass for (optional) GNU Emacs support of
-# your package. This is NOT for XEmacs!
+# your package. This is NOT for XEmacs!
# Many of the steps here are sometimes done by the build system of your
# package (especially compilation), so this is mainly for standalone elisp
# files you gathered from somewhere else.
# elisp-comp *.el || die "elisp-comp failed!"
#
# Function elisp-make-autoload-file() can be used to generate a file with
-# autoload definitions for the lisp functions. It takes the output file name
+# autoload definitions for the lisp functions. It takes the output file name
# (default: "${PN}-autoloads.el") and a list of directories (default: working
-# directory) as its arguments. Use of this function requires that the elisp
+# directory) as its arguments. Use of this function requires that the elisp
# source files contain magic ";;;###autoload" comments. See the Emacs Lisp
# Reference Manual (node "Autoload") for a detailed explanation.
#
#
# To let the Emacs support be activated by Emacs on startup, you need
# to provide a site file (shipped in ${FILESDIR}) which contains the startup
-# code (have a look in the documentation of your software). Normally this
+# code (have a look in the documentation of your software). Normally this
# would look like this:
#
# ;;; csv-mode site-lisp configuration
# If your Emacs support files are installed in a subdirectory of
# /usr/share/emacs/site-lisp/ (which is recommended if more than one file is
# installed), you need to extend Emacs' load-path as shown in the first
-# non-comment. The elisp-site-file-install() function of this eclass will
+# non-comment. The elisp-site-file-install() function of this eclass will
# replace "@SITELISP@" by the actual path.
# The next line tells Emacs to load the mode opening a file ending with
# ".csv" and load functions depending on the context and needed features.
# Be careful though. Commands as "load-library" or "require" bloat the
# editor as they are loaded on every startup. When having a lot of Emacs
-# support files, users may be annoyed by the start-up time. Also avoid
-# keybindings as they might interfere with the user's settings. Give a hint
+# support files, users may be annoyed by the start-up time. Also avoid
+# keybindings as they might interfere with the user's settings. Give a hint
# in pkg_postinst(), which should be enough.
# The naming scheme for this site file is "[0-9][0-9]*-gentoo.el", where the
-# two digits at the beginning define the loading order. So if you depend on
+# two digits at the beginning define the loading order. So if you depend on
# another Emacs package, your site file's number must be higher!
# Best practice is to define a SITEFILE variable in the global scope of your
# ebuild (right after DEPEND e.g.):
#
# elisp-site-file-install "${FILESDIR}/${SITEFILE}"
#
-# in src_install(). If your subdirectory is not named ${PN}, give the
+# in src_install(). If your subdirectory is not named ${PN}, give the
# differing name as second argument.
#
# pkg_postinst() / pkg_postrm() usage:
ls ${ROOT}${SITELISP}/[0-9][0-9]*-gentoo.el | sort -n | \
while read sf
do
- einfo " Adding $(basename $sf) ..."
+ einfo " Adding $(basename $sf) ..."
# Great for debugging, too noisy and slow for users though
# echo "(message \"Loading $sf ...\")" >>${ROOT}${SITELISP}/site-start.el
cat $sf >>${ROOT}${SITELISP}/site-gentoo.el
projects / gentoo.git / commitdiff