* feat(fortran): account for f90 and fortran modes
* feat(fortran): initial keybindings
* feat(fortran): basic compilation
* feat(fortran): compilation popup
This customizes the name of the compilation buffer produced by the
`compile` function. We're keeping things simple; Emacs already knows how
to run compilation commands in a popup and parse the results, so let's
let it do its thing.
* feat(fortran): doctor checks
* docs(fortran): installation instructions
* feat(fortran): actual usage of fpm
* feat(fortran): configure compilation popups
* feat(fortran): improved raw gfortran usage
Although it's recommended to do everything through `fpm` to make life
easier.
* docs(fortran): backburner `+intel` for now
* feat(fortran): address PR suggestions
- Rename module from `:completion selectrum` to `:completion vertico`
- Rename all files involved
- Do *not* yet rename all the functions, as that messes up git's rename
detection.
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.
