Emacs 27.x has been the stable version of Emacs for nearly a year, and
introduces a litany of bugfixes, performance, and quality-of-life
improvements that significantly reduce Doom's maintenance burden (like
XDG support, early-init.el, image manipulation without imagemagick, a
native JSON library, harfbuzz support, pdumper, and others).
With so many big changes on Doom's horizon, I like having one less (big)
thing to worry about.
Also reverts bb677cf7a (#5232) as it is no longer needed.
- Moves clipetty to its own, opt-in module (#2671, #3195, #3498)
- Fix cursor shape changing between evil states (#1994)
- Moves `xterm-mouse-mode` and `visible-cursor` config out of core.
Another set of fixes to the minimap as suggested by @hlissner.
- Changed the use-package to :defer t
- Updated the README.org and removed the Hacks section
- Alphabetized the init.example.el list
Created a new Minimap module based on minimap.el from ELPA
the module sets some DOOM-specific config, and better defaults.
Also added keybindings for it.
An effort to reduce the number of packages for first-time install. These
features aren't critical to the UX or character of Doom Emacs, so I've
made them opt-in.
The non-LSP stack (gocode) appears to be unmaintained and is a poor
experience. Could use some help from go users to figure out which of the
dependencies in the lang/go's readme should be installed with gopls.
I understand this makes them a mote more difficult to discover, but I'd
argue neither +dragndrop or +present are necessary defaults, and this
wasn't a comrpehensive list anyway.
Fewer packages to install on first install.
+ Disable multiple-cursors, rotate-text, and ibuffer modules by default;
these are not essential.
+ Make :ui popup's `+all` flag opt-in (so the popup manager doesn't
manage buffers without an explicit rule -- which is more disruptive
than helpful).
+ Make :tools lookup's `+docsets` flag opt-in
- Pressing gd on a module in your doom! block will now browse that
module's directory.
- Pressing K on a module will jump to that module's documentation, if any.
- Pressing K on a module flag will jump to that flag's description
within that module's documenation.
- This is now explained in init.example.el
Closes#2249