Emacs config utilizing prelude as a base
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

31 lines
1.6 KiB

5 years ago
5 years ago
  1. # Frequently Asked Questions
  2. ## What's the origin of the name Emacs Prelude?
  3. I wanted an Emacs experience that was both as sleek and as powerful
  4. as the legendary sports car [Honda Prelude](https://en.wikipedia.org/wiki/Honda_Prelude).
  5. I also wanted a name with `el` in it. :-)
  6. ## Why doesn't Prelude use `use-package`?
  7. While `use-package` provides a nice way of structuring your
  8. configuration (especially if you're into single-file setups), it also adds a layer of complexity as it's just a macro
  9. that expands to some "traditional" configuration code. One aspect of `use-package` that's a bit tricky is where to place cross-package configuration, as it can potentially go to different configuration blocks.
  10. Given how modular the structure of Prelude is, there's relatively little to be gained by adopting `use-package` everywhere, but end users are free to use `use-package` for their personal configuration.
  11. !!! Note
  12. I have a stripped-down version of Prelude for personal use, based on `use-package` [here](https://github.com/bbatsov/emacs.d).
  13. I guess it might be of interest to some of you.
  14. ## Why does Prelude use MELPA instead of MELPA Stable by default?
  15. Mostly because many package authors/maintainers don't have the habit to cut
  16. "stable" releases of their projects. It seems that's changing for the better
  17. in recent years, so Prelude's defaults might change down the road.
  18. ## Why is Zenburn the default color theme?
  19. No particular reason other than the fact that I like it a lot and happen to maintain
  20. its Emacs port. I believe it's pretty nice improvement over the default Emacs theme, but your perspective might be different.