One of the problems\u2014perhaps the major problem\u2014that a new Emacs user faces is building an initial configuration. One would think that a vanilla install would be a good starting point for a new user but we all know that that initial install is not going to deliver a very good experience. Mostly that’s because even if you’re interested in Emacs strictly as an editor, it’s most usefully thought of as an editor construction kit. Even at the start, you need to do a bit of customization. <\/p>\n
Huy Tran has a post that can help the n00b out. His post, Emacs from scratch<\/a>, outlines a minimal configuration to get the new user going. It’s oriented towards a Spacemacs<\/a>-like setup but even a relative new user should be able to include or exclude those parts as desired. <\/p>\n The major parts of the configuration are: <\/p>\n He also configures a bit of macOS specific data that a new user probably shouldn’t worry about. <\/p>\n I disagree with the Helm installation, not because there’s anything wrong with Helm (although I prefer Ivy) but because it’s not something a n00b should be worrying about initially. I also don’t care for If you know someone who’s new to Emacs and looking for an initial configuration to get started, this is a good resource. <\/p>\n","protected":false},"excerpt":{"rendered":" One of the problems\u2014perhaps the major problem\u2014that a new Emacs user faces is building an initial configuration. One would think that a vanilla install would be a good starting point for a new user but we all know that that … Continue reading \n
use-package<\/code> macro is loaded.<\/li>\nwhich-key<\/code>.<\/li>\nprojectile<\/code>.<\/li>\nneotree<\/code> and icons.<\/li>\n<\/ul>\nneotree<\/code> but perhaps it’s helpful for n00bs and it probably doesn’t hurt to install it. <\/p>\n