spacemacs/core/templates/packages.el.template

;;; packages.el --- %LAYERNAME% Layer packages File for Spacemacs
;;
;; Copyright (c) 2012-2014 Sylvain Benner
;; Copyright (c) 2014-2015 Sylvain Benner & Contributors
;;
;; Author: Sylvain Benner <sylvain.benner@gmail.com>
;; URL: https://github.com/syl20bnr/spacemacs
;;
;; This file is not part of GNU Emacs.
;;
;;; License: GPLv3

;; List of all packages to install and/or initialize. Built-in packages
;; which require an initialization must be listed explicitly in the list.
(setq %LAYERNAME%-packages
    '(
      ;; package names go here
      ))

;; List of packages to exclude.
(setq %LAYERNAME%-excluded-packages '())

;; For each package, define a function %LAYERNAME%/init-<package-name>
;;
;; (defun %LAYERNAME%/init-my-package ()
;;   "Initialize my package"
;;   )
;;
;; Often the body of an initialize function uses `use-package'
;; For more info on `use-package', see readme:
;; https://github.com/jwiegley/use-package
Use weirder-looking templating variables It's important to make templating variables something unique-looking so that you don't accidentally write template variables where you don't mean to. For example, in extensions.template, "package names go here" was being replaced with "package <name of package>s go here", etc. Also Search case-insensitively for good measure 2015-06-02 00:23:05 +00:00			`;;; packages.el --- %LAYERNAME% Layer packages File for Spacemacs`
Update CONTRIBUTE.md and add file headers Also add default file header to layer templates. 2015-01-14 04:12:56 +00:00			`;;`
			`;; Copyright (c) 2012-2014 Sylvain Benner`
			`;; Copyright (c) 2014-2015 Sylvain Benner & Contributors`
			`;;`
			`;; Author: Sylvain Benner <sylvain.benner@gmail.com>`
			`;; URL: https://github.com/syl20bnr/spacemacs`
			`;;`
			`;; This file is not part of GNU Emacs.`
			`;;`
			`;;; License: GPLv3`

Replace defvar with setq for pre and post extensions variables 2015-04-19 03:57:27 +00:00			`;; List of all packages to install and/or initialize. Built-in packages`
			`;; which require an initialization must be listed explicitly in the list.`
Use weirder-looking templating variables It's important to make templating variables something unique-looking so that you don't accidentally write template variables where you don't mean to. For example, in extensions.template, "package names go here" was being replaced with "package <name of package>s go here", etc. Also Search case-insensitively for good measure 2015-06-02 00:23:05 +00:00			`(setq %LAYERNAME%-packages`
Update layer templates. 2015-05-26 07:23:47 +00:00			`'(`
			`;; package names go here`
			`))`
Add function to create a new configuration layer 2014-11-22 05:08:44 +00:00
Replace defvar with setq for pre and post extensions variables 2015-04-19 03:57:27 +00:00			`;; List of packages to exclude.`
Use weirder-looking templating variables It's important to make templating variables something unique-looking so that you don't accidentally write template variables where you don't mean to. For example, in extensions.template, "package names go here" was being replaced with "package <name of package>s go here", etc. Also Search case-insensitively for good measure 2015-06-02 00:23:05 +00:00			`(setq %LAYERNAME%-excluded-packages '())`
Add function to create a new configuration layer 2014-11-22 05:08:44 +00:00
Use weirder-looking templating variables It's important to make templating variables something unique-looking so that you don't accidentally write template variables where you don't mean to. For example, in extensions.template, "package names go here" was being replaced with "package <name of package>s go here", etc. Also Search case-insensitively for good measure 2015-06-02 00:23:05 +00:00			`;; For each package, define a function %LAYERNAME%/init-<package-name>`
Add function to create a new configuration layer 2014-11-22 05:08:44 +00:00			`;;`
Use weirder-looking templating variables It's important to make templating variables something unique-looking so that you don't accidentally write template variables where you don't mean to. For example, in extensions.template, "package names go here" was being replaced with "package <name of package>s go here", etc. Also Search case-insensitively for good measure 2015-06-02 00:23:05 +00:00			`;; (defun %LAYERNAME%/init-my-package ()`
Add function to create a new configuration layer 2014-11-22 05:08:44 +00:00			`;; "Initialize my package"`
			`;; )`
			`;;`
			;; Often the body of an initialize function uses `use-package'
			;; For more info on `use-package', see readme:
			`;; https://github.com/jwiegley/use-package`