setup
- Description
- Helpful Configuration Macro
- Latest
- setup-1.4.0.tar (.sig), 2024-Apr-13, 80.0 KiB
- Maintainer
- Philip Kaludercic <~pkal/public-inbox@lists.sr.ht>
- Atom feed
- setup.xml
- Website
- https://git.sr.ht/~pkal/setup
- Browse ELPA's repository
- CGit or Gitweb
- Badge
To install this package from Emacs, use package-install
or list-packages
.
Full description
The `setup' macro simplifies repetitive configuration patterns, by providing context-sensitive local macros in `setup' bodies. These macros can be mixed with regular elisp code without any issues, allowing for flexible and terse configurations. The list of local macros can be extended by the user via `setup-define'. A list of currently known local macros are documented in the docstring for `setup'. Examples and extended documentation can be found on Emacs wiki: https://www.emacswiki.org/emacs/SetupEl. Please feel free to contribute your own local macros or ideas.
Old versions
setup-1.3.2.tar.lz | 2024-Mar-31 | 18.2 KiB |
setup-1.3.1.tar.lz | 2022-Sep-15 | 18.2 KiB |
setup-1.3.0.tar.lz | 2022-Jun-12 | 18.4 KiB |
setup-1.2.0.tar.lz | 2021-Nov-08 | 17.9 KiB |
setup-1.1.0.tar.lz | 2021-Oct-01 | 17.5 KiB |
setup-1.0.1.tar.lz | 2021-Sep-25 | 17.2 KiB |
setup-1.0.0.tar.lz | 2021-Aug-19 | 17.2 KiB |
setup-0.2.1.tar.lz | 2021-Jul-01 | 16.9 KiB |
setup-0.2.0.tar.lz | 2021-Apr-19 | 16.2 KiB |
setup-0.1.2.tar.lz | 2021-Mar-25 | 15.6 KiB |
setup-0.1.1.tar.lz | 2021-Mar-16 | 15.4 KiB |
News
Version 1.4.0 (13Apr24) - New :bind-to macro, that takes a key chord and binds the context-relevant function. E.g. (setup (:package do-at-point) (:bind-to "C-'")) - New :autoload-this creates an auto-load cookie for the context-relevant function by connecting it to the context-relevant feature. - Avoid calling `package-refresh-contents' in :package if it is not necessary. The check here was broken, as Ralf Schmitt noticed. - Earl Hyatt improved the :repeatable keyword to support a prefix of non-repeating arguments. - Passing a map to :bind-into has been deprecated, since there is no reliable way to deduce the feature that holds the map. I apologise for the inconvenience. The functionality will remain for a while, but I would advise rewriting affected configuration.