spacemacs/layers/+completion/ivy/layers.el

;;; layers.el --- Ivy Layer layers File for Spacemacs
;;
;; Copyright (c) 2012-2020 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

(configuration-layer/declare-shadow-relation 'ivy 'helm)

;; smex is handled by the `ivy' layer and we don't want
;; to use the ownership mechanism of layers because it is dependent
;; on the order of layer declaration
(configuration-layer/remove-layer 'smex)
ivy: create missing layers.el file Was triggering an error if ivy and smex layer were both used at the same time and smex layer stole ownership of smex package. Fixes #6281 2016-06-11 00:50:39 +00:00			`;;; layers.el --- Ivy Layer layers File for Spacemacs`
			`;;`
update copyright to 2020 2020-09-16 21:34:40 +00:00			`;; Copyright (c) 2012-2020 Sylvain Benner & Contributors`
ivy: create missing layers.el file Was triggering an error if ivy and smex layer were both used at the same time and smex layer stole ownership of smex package. Fixes #6281 2016-06-11 00:50:39 +00:00			`;;`
			`;; Author: Sylvain Benner <sylvain.benner@gmail.com>`
			`;; URL: https://github.com/syl20bnr/spacemacs`
			`;;`
			`;; This file is not part of GNU Emacs.`
			`;;`
			`;;; License: GPLv3`

core: refactor shadow mechanism Shadowing is now control by layer property ':can-shadow' only. can-shadow is a commutative relation, if layer1 can shadow layer2 then layer2 can shadow layer1. the shadow operator is a binary operator accepting two layer names, it is not commutative and the order of the operands is determined by the order of the layers in the dotfile (like the ownership stealing mechanism). If ':can-shadow' is set explicity to nil in the dotfile then the layer won't shadow any layer. For instance to install both ivy and helm layer: (setq dotspacemacs-configuration-layers '( ivy (helm :can-shadow nil) ) note that due to the commutative relation the above example can also be written (in this case, ':can-shadow' should be read ':can-be-shawdowed'): (setq dotspacemacs-configuration-layers '( (ivy :can-shadow nil) helm ) 2017-09-26 02:55:08 +00:00			`(configuration-layer/declare-shadow-relation 'ivy 'helm)`
core: add layer shadowing system Layers can now declare in their layers.el file that they shadow one or more layers using the following functions: - configuration-layer/shadow-layers - configuration-layer/shadow-layer Those function are commutative so: (configuration-layer/shadow-layer 'layer1 'layer2) is the same as (configuration-layer/shadow-layer 'layer2 'layer1) and means that layer1 shadows layer2 and layer2 shadows layer1 The typical use-case is helm and ivy layers. Helm shadows the ivy layer and Ivy shadows the helm layer. Shadowing is sensitive to the order of declaration of layers in the dotfile, for instance: (setq dotspacemacs-configuration-layers '( helm ivy )) means that ivy shadows helm so helm layer is effectively ignored, whereas (setq dotspacemacs-configuration-layers '( ivy helm )) means that helm shadows ivy so ivy layer is effectively ignored. This mechanism can be turned off using the :can-shadow keyword: (setq dotspacemacs-configuration-layers '( ivy (helm :can-shadow nil) )) means that both ivy and helm layers will be installed (not recommended in this case) Note that the `:can-shadow` mechanism will be fully implemented in a next commit. 2017-09-22 03:47:20 +00:00
ivy: create missing layers.el file Was triggering an error if ivy and smex layer were both used at the same time and smex layer stole ownership of smex package. Fixes #6281 2016-06-11 00:50:39 +00:00			;; smex is handled by the `ivy' layer and we don't want
			`;; to use the ownership mechanism of layers because it is dependent`
			`;; on the order of layer declaration`
			`(configuration-layer/remove-layer 'smex)`