about summary refs log tree commit diff
path: root/parse.nix
Commit message (Collapse)AuthorAge
* Allow `leaf` to be used as an alternative to `use-package`..talyz2020-12-27
| | | | ..in `emacsWithPackagesFromUsePackage`.
* Add `alwaysTangle` argument to emacsWithPackagesFromUsePackagetalyz2020-08-11
| | | | | Add an option to tangle all Org mode babel code blocks by default and update the documentation.
* Use the native Org mode parsing capabilities of fromElisp...talyz2020-08-07
| | | | ..for IFD free Org babel file support.
* correctly formatLuke Bentley-Fox2020-07-24
| | | Co-authored-by: Kim Lindberger <kim.lindberger@gmail.com>
* use fixed package setLuke Bentley-Fox2020-07-24
|
* Use an update script to import fromElisptalyz2020-07-22
|
* Add option use-package-always-ensure behaviortalyz2020-07-18
| | | | | | | When `use-package-always-ensure` is set to `t`, `:ensure` defaults to `t`. This adds the `alwaysEnsure` argument to `emacsWithPackagesFromUsePackage` which, if set to true, emulates this behavior.
* Make parsePackagesFromUsePackage consider :ensure and :disabledtalyz2020-07-18
| | | | | | | | | | | | | Use `fromElisp` (https://github.com/talyz/fromElisp), imported using `niv` (https://github.com/nmattia/niv), to properly parse the emacs configuration. This lets us take `:ensure` and `:disabled` into account when listing packages to install: - only declarations with an `:ensure` value of true or an alternate package name will be included; if an alternate package name is supplied, it will be used - declarations with a `:disabled` value of true will be excluded
* Renamed packageFile arg to packageElisp for claritySteve Purcell2020-06-21
|
* Add docstring with example Package-Requires parse inputs and resultsSteve Purcell2020-06-20
|
* Match more liberally in Package-Requires listsSteve Purcell2020-06-20
|
* Add emacsWithPackagesFromPackageRequiresSteve Purcell2020-06-20
This provides a mechanism for creating an Emacs closure that contains the runtime dependencies for a given Emacs package source file, by inspecting its Package-Requires header.