All Projects → josteink → Emacs Oob Reboot

josteink / Emacs Oob Reboot

A project to revitalize Emacs by providing core-friendly changes for an improved out-of-the-box experience

Labels

Projects that are alternatives of or similar to Emacs Oob Reboot

Org Zettelkasten
An opinionated setup for managing large collections of interlinked org files.
Stars: ✭ 77 (-9.41%)
Mutual labels:  emacs
Clj Suitable
ClojureScript "IntelliSense" support for JS objects and their properties/methods. Via figwheel and Emacs CIDER.
Stars: ✭ 82 (-3.53%)
Mutual labels:  emacs
Fmacs
Emacs clone in Forth.
Stars: ✭ 84 (-1.18%)
Mutual labels:  emacs
Hexo.el
Use Hexo in Emacs elegantly
Stars: ✭ 78 (-8.24%)
Mutual labels:  emacs
Ripgrep.el
Emacs front-end for ripgrep, a command line search tool
Stars: ✭ 81 (-4.71%)
Mutual labels:  emacs
Beginend
Emacs package to redefine M-< and M-> for some modes
Stars: ✭ 82 (-3.53%)
Mutual labels:  emacs
.emacs.d
My emacs configuration
Stars: ✭ 76 (-10.59%)
Mutual labels:  emacs
Makem.sh
Makefile-like script for building and testing Emacs Lisp packages
Stars: ✭ 85 (+0%)
Mutual labels:  emacs
Sensible Defaults.el
A simple, modular collection of better Emacs default settings.
Stars: ✭ 81 (-4.71%)
Mutual labels:  emacs
Org Wild Notifier.el
Alert notifications for org-agenda
Stars: ✭ 84 (-1.18%)
Mutual labels:  emacs
Emacs Sql Indent
Syntax based indentation for SQL files inside GNU Emacs
Stars: ✭ 78 (-8.24%)
Mutual labels:  emacs
Corral
Quickly surround text with delimiters in emacs
Stars: ✭ 80 (-5.88%)
Mutual labels:  emacs
Emacs Chocolate Theme
🍫A dark chocolatey theme for Emacs 🍫
Stars: ✭ 83 (-2.35%)
Mutual labels:  emacs
Guess Language.el
Emacs minor mode that detects the language you're typing in. Automatically switches spell checker. Supports multiple languages per document.
Stars: ✭ 78 (-8.24%)
Mutual labels:  emacs
Dumb Jump
an Emacs "jump to definition" package for 50+ languages
Stars: ✭ 1,256 (+1377.65%)
Mutual labels:  emacs
Embrace.el
Add/Change/Delete pairs based on `expand-region', similar to `evil-surround'.
Stars: ✭ 76 (-10.59%)
Mutual labels:  emacs
Tide
Tide - TypeScript Interactive Development Environment for Emacs
Stars: ✭ 1,238 (+1356.47%)
Mutual labels:  emacs
Vterm Toggle
toggles between the vterm buffer and whatever buffer you are editing.
Stars: ✭ 85 (+0%)
Mutual labels:  emacs
Emacsideas
Porting some great extensions of emacs to Intellij IDEA. such as AceJump, CopyWithoutSelection.
Stars: ✭ 84 (-1.18%)
Mutual labels:  emacs
.emacs.d
Centaur Emacs - A Fancy and Fast Emacs Configuration
Stars: ✭ 1,251 (+1371.76%)
Mutual labels:  emacs

emacs-oob-reboot

This is a project which aims to revitalize Emacs by providing core-friendly changes for an improved out-of-the-box experience.

You can help, and you don't need to know a single bit of C! But how? Read on!

background

For Emacs to remain healthy sustainable for another 40+ years, we need to keep a critical mass of users and developers. To ensure this, we need to attract new users.

"Everyone" in the Emacs-verse seems to agree Emacs is the world's most powerful editor, yet other editors are seeing much higher adaptation than Emacs.

Emacs, despite all its power, does not impress out of the box. A user will need to know that:

  1. it can be customized, and
  2. find all these customization to turn it into a more productive environment.

While this isn't a problem for "senior" Emacs-users which are already customized left and right, this probably hinders adaptation by new users.

After a brief discussion with phillord and other's on #Emacs on Freenode, we agreed that to better attract new user, Emacs could benefit from an improved out of the box experience.

the "historical" response

The standard reply to this issue has long been that it's good for a user to go through such a process, that a user should in fact do so, so they can find out how they can make their Emacs more productive for them. And if a user can't be bothered to do that, he probably won't "get" Emacs anyway, so no loss to us.

But is this really a productive attitude?

Looking at pretty much all other editors out which are seeing increased adaptation, they have a few things in common:

  • A polished look and feel, out of the box
  • A reasonable and useful set of default settings, out of the box
  • Core features and packages installed, out of the box

Seemingly the default "out of the box"-configuration seems to matter.

the goal and the means

Basically, in 2017, the best the 1995 has to offer does not cut it as a default-experience. It's time we make some improvements.

The aim for this project is not to mimick a big "starter"-kit like prelude, but instead try to improve the out of the box experience by making small, core-friendly changes, so that these changes have a chance to be merged back mainline.

Such changes may for instance consist of:

  • new values for existing defconst, defvar and setq-statements
  • by default installing/bundling packages from ELPA
  • useful default-behaviours implemented through default mode-hooks
  • any combination of those
  • etc

ways to help this project

There are numerous ways you can help this project:

  1. Evaluate it's current state. Does it work? Are any of the changes overly opiniated? Let us know!
  2. Monitor issues and PRs. Help review them.
  3. Submitting changes.
  4. Spread the word: Anywhere. To anyone you think can contribute! The more eyes this project has, the more chances we have of getting useful improvements, and reaching a good consensus on the changes we propose.

Feel free to sign up as a contributor. A special issue has been reserved for this very purpose.

evaluating the current setup

To evaluate the current setup you'll need to launch Emacs in a special way.

Do so by issuing the following commands:

git clone https://github.com/josteink/emacs-oob-reboot
cd emacs-oob-reboot
emacs -Q -l ./init.el

You are now running our "improved" Emacs default experience.

submitting improvements

Submitting improvements should be easy:

  1. Go scan your .emacs-file and find your essential customizations which you think should be a default.
  2. Fork this repo.
  3. Follow the existing conventions, and add your changes. See CONTRIBUTING.org.
  4. Submit a PR. In this PR you should try to make each customization/improvement an atomic commit, and maybe even a PR on its own. This will assist review.

anything else?

Did I forget anything? File an issue, file a PR. It's github. You know the rules :)

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].