emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
doomemacs/core/packages.el

46 lines
2 KiB
EmacsLisp
Raw Normal View History

Refactor package management system
2017-02-11 00:46:42 -05:00
;; -*- no-byte-compile: t; -*-
;;; core/packages.el
:boom: Replace exec-path-from-shell w/ 'bin/doom env' IMPORTANT: This is a breaking update for Mac users, as your shell environment will no longer be inherited correctly (with the removal of exec-path-from-shell). The quick fix is: 'bin/doom env refresh'. Also, the set-env! autodef now does nothing (and is deprecated), be sure to remove calls to it in your config. Smaller changes: + This update also adds --no-* switches to doom quickstart + Includes general improvements to the documentation of several bin/doom commands. + Moves doom/reload* commands to core/autoload/config.el + doom/reload-project has been removed (it didn't actually do anything) The breaking change: This update adds an "envvar file" to Doom Emacs. This file is generated by `doom env refresh`, populated with variables scraped from your shell environment (from both non-interactive and interactive sessions). This file is then (inexpensively) loaded at startup, if it exists. + The file is manually generated with `doom env refresh`. + It can be regenerated automatically whenever `doom refresh` is run by running `doom env enable` (`doom env clear` will reverse this and delete the env file). + `doom quickstart` will ask if you want to auto-generate this envvar file. You won't need it if you're confident Emacs will always be started from the correct environment, however. + Your env file can be reloaded from a running Emacs session with `M-x doom/reload-env`. Note: this won't work if the Emacs session you're running it in doesn't have a correct SHELL set. i.e. don't use this to create your first env file! The idea isn't mine -- it's borrowed from Spacemacs -- and was introduced to me in #1053 by @yurimx. I was impressed with it. Prior to this, I was unhappy with exec-path-from-shell (no hate to the dev, I understand its necessity), and 'doom patch-macos' wasn't ideal for mac users (needed to be reapplied every time you update Emacs). What's more, many users (even Linux users) had to install exec-path-from-shell anyway. This solution suffers from none of their shortcomings. More reliable than patch-macos, more performant and complete than exec-path-from-shell, and easily handled by bin/doom.
2019-03-28 00:06:10 -04:00
;; core.el
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! auto-minor-mode :pin "17cfa1b54800fdef2975c0c0531dad34846a5065")
(package! gcmh :pin "b1bde5089169a74f62033d027e06e98cbeedd43f")
:boom: Replace exec-path-from-shell w/ 'bin/doom env' IMPORTANT: This is a breaking update for Mac users, as your shell environment will no longer be inherited correctly (with the removal of exec-path-from-shell). The quick fix is: 'bin/doom env refresh'. Also, the set-env! autodef now does nothing (and is deprecated), be sure to remove calls to it in your config. Smaller changes: + This update also adds --no-* switches to doom quickstart + Includes general improvements to the documentation of several bin/doom commands. + Moves doom/reload* commands to core/autoload/config.el + doom/reload-project has been removed (it didn't actually do anything) The breaking change: This update adds an "envvar file" to Doom Emacs. This file is generated by `doom env refresh`, populated with variables scraped from your shell environment (from both non-interactive and interactive sessions). This file is then (inexpensively) loaded at startup, if it exists. + The file is manually generated with `doom env refresh`. + It can be regenerated automatically whenever `doom refresh` is run by running `doom env enable` (`doom env clear` will reverse this and delete the env file). + `doom quickstart` will ask if you want to auto-generate this envvar file. You won't need it if you're confident Emacs will always be started from the correct environment, however. + Your env file can be reloaded from a running Emacs session with `M-x doom/reload-env`. Note: this won't work if the Emacs session you're running it in doesn't have a correct SHELL set. i.e. don't use this to create your first env file! The idea isn't mine -- it's borrowed from Spacemacs -- and was introduced to me in #1053 by @yurimx. I was impressed with it. Prior to this, I was unhappy with exec-path-from-shell (no hate to the dev, I understand its necessity), and 'doom patch-macos' wasn't ideal for mac users (needed to be reapplied every time you update Emacs). What's more, many users (even Linux users) had to install exec-path-from-shell anyway. This solution suffers from none of their shortcomings. More reliable than patch-macos, more performant and complete than exec-path-from-shell, and easily handled by bin/doom.
2019-03-28 00:06:10 -04:00
Refactor package management system
2017-02-11 00:46:42 -05:00
;; core-ui.el
Bump :core Wilfred/helpful@c54e9dd -> Wilfred/helpful@c0662aa bbatsov/projectile@5cd261d -> bbatsov/projectile@768f057 domtronn/all-the-icons.el@0b74fc3 -> domtronn/all-the-icons.el@d6cb6d4 jscheid/dtrt-indent@9163cd9 -> jscheid/dtrt-indent@50c440c
2020-05-12 21:41:05 -04:00
(package! all-the-icons :pin "d6cb6d4a779eaa3570d8e451fd4d38b2b4554860")
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! hide-mode-line :pin "88888825b5b27b300683e662fa3be88d954b1cea")
(package! highlight-numbers :pin "8b4744c7f46c72b1d3d599d4fb75ef8183dee307")
Use long SHA1 for rainbow-delimiters
2020-04-30 01:38:52 -04:00
(package! rainbow-delimiters :pin "5125f4e47604ad36c3eb4706310fcafac729ca8c")
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! restart-emacs :pin "9aa90d3df9e08bc420e1c9845ee3ff568e911bd9")
Refactor package management system
2017-02-11 00:46:42 -05:00
;; core-editor.el
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! better-jumper :pin "6d240032ca213ccb3347e25f26c29b6822bf03a7")
Bump :core Wilfred/helpful@c54e9dd -> Wilfred/helpful@c0662aa bbatsov/projectile@5cd261d -> bbatsov/projectile@768f057 domtronn/all-the-icons.el@0b74fc3 -> domtronn/all-the-icons.el@d6cb6d4 jscheid/dtrt-indent@9163cd9 -> jscheid/dtrt-indent@50c440c
2020-05-12 21:41:05 -04:00
(package! dtrt-indent :pin "50c440c80e0d15303d8ab543bce4c56e9c2bf407")
(package! helpful :pin "c0662aa07266fe204f4e6d72ccaa6af089400556")
Disable ns-auto-titlebar & xclip properly on other OSes
2020-01-06 15:07:13 -05:00
(when IS-MAC
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! ns-auto-titlebar :pin "1efc30d38509647b417f05587fd7003457719256"))
(package! pcre2el :pin "0b5b2a2c173aab3fd14aac6cf5e90ad3bf58fa7d")
(package! smartparens :pin "555626a43f9bb1985aa9a0eb675f2b88b29702c8")
Add so-long package This package kicks in if you open a file whose lines are too long. It is built into Emacs 27+, but I've backported it for earlier users.
2019-07-21 04:12:01 +02:00
(package! so-long
Minor refactors & comment revision
2020-01-02 21:13:31 -05:00
:built-in 'prefer ; included in Emacs 27+
Use personal mirror for so-long package #1707 Until so-long is published to ELPA (if ever), we're now using my personal mirror for so-long. Why not git.savannah.nongnu.org instead? Because it runs on a potato too.
2019-09-09 15:44:09 -04:00
;; REVIEW so-long is slated to be published to ELPA eventually, but until then
Minor refactors & comment revision
2020-01-11 17:27:04 -05:00
;; I've created my own mirror for it because git.savannah.gnu.org runs
;; on a potato.
PIN ALL THE PACKAGES
2020-01-14 22:32:11 -05:00
:recipe (:host github :repo "hlissner/emacs-so-long")
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
:pin "ed666b0716f60e8988c455804de24b55919e71ca")
Use my fork of ws-butler
2020-01-04 18:10:55 -05:00
(package! ws-butler
;; Use my fork of ws-butler, which has a few choice improvements and
;; optimizations (the original has been abandoned).
PIN ALL THE PACKAGES
2020-01-14 22:32:11 -05:00
:recipe (:host github :repo "hlissner/ws-butler")
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
:pin "2bb49d3ee7d2cba133bc7e9cdac416cd1c5e4fe0")
Disable ns-auto-titlebar & xclip properly on other OSes
2020-01-06 15:07:13 -05:00
(unless IS-WINDOWS
Add clipetty for TTY users.
2020-03-16 23:00:16 +01:00
(package! clipetty
:recipe (:host github :repo "spudlyo/clipetty")
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
:pin "01b39044b9b65fa4ea7d3166f8b1ffab6f740362"))
Refactor package management system
2017-02-11 00:46:42 -05:00
;; core-projects.el
Bump :core Wilfred/helpful@c54e9dd -> Wilfred/helpful@c0662aa bbatsov/projectile@5cd261d -> bbatsov/projectile@768f057 domtronn/all-the-icons.el@0b74fc3 -> domtronn/all-the-icons.el@d6cb6d4 jscheid/dtrt-indent@9163cd9 -> jscheid/dtrt-indent@50c440c
2020-05-12 21:41:05 -04:00
(package! projectile :pin "768f0570cad57b6885c4472df803906d097cbc1a")
Add core-keybinds.el
2017-02-19 07:03:05 -05:00
;; core-keybinds.el
Bump :core spudlyo/clipetty@7ee3f9c -> spudlyo/clipetty@01b3904 bbatsov/projectile@eec569d -> bbatsov/projectile@5cd261d noctuid/general.el@14ad4c8 -> noctuid/general.el@42e3803 We're also transitioning from abbreviated SHA1 hashes to full ones, because underlying git machinery in future updates of straight will require it (e.g. to obtain shallow clones of pinned packages).
2020-04-29 23:09:46 -04:00
(package! general :pin "42e38034cd2305fa7432866323c923979d8f9b06")
(package! which-key :pin "8b49ae978cceca65967f3544c236f32964ddbed0")
Reference in a new issue Copy permalink