From 080e530b4a1ac1d07d247d1f49010dfcd6bd2723 Mon Sep 17 00:00:00 2001 From: "Tom Breton (Tehom)" Date: Fri, 12 Nov 2010 12:02:19 -0500 Subject: [PATCH] Minor edits to README --- README.org | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/README.org b/README.org index 3b723ca..63154ab 100644 --- a/README.org +++ b/README.org @@ -3,6 +3,9 @@ #+BLOGLABELS: * README for elinstall +** What it is + +An installer for elisp code. It sets up autoloads, load-path, etc. ** Why use it @@ -17,6 +20,9 @@ with emacs. Why use elinstall? Because: * Unlike autoload.el, it can also set up load-path and Info-default-directory-list (that's like load-path for info files) + * Unlike autoload.el, it's not focussed on building emacs, it's + focussed on installing elisp. + * Unlike some other installers, it works with canonical loaddefs.el-style autoload files. @@ -27,8 +33,11 @@ with emacs. Why use elinstall? Because: But it also works well for packages. - * Because internally it works in articulated stages, it's easier to + * Since internally it works in articulated stages, it's easier to hack and extend than autoload.el +** Where to get it + +It lives at http://repo.or.cz/w/elinstall.git]] ** How to use it @@ -57,15 +66,15 @@ Write a call like this: (elinstall "project-buffer-mode" (elinstall-directory-true-name) - '(def-file "project-buffer-loaddefs.el" - (all + '(all (dir "./") (dir "plugins/") - (dir "extensions/")))) + (dir "extensions/"))) #+END_src -It can actually be executed every time, because elinstall checks for -already-installed packages. +You don't have to check whether it's already been installed, because +elinstall remembers which packages it has installed and doesn't +install them again. CAUTION: `elinstall-directory-true-name' is sensitive to where it's called. That's the point of it -- 2.11.4.GIT