Code Monkey home page Code Monkey logo

.emacs.d's Introduction

The software that transcends time

A few years ago, a co-worker adviced to get started with vanilla Emacs. It made a lot of sense because I was writing Clojure. Emacs has now become my goto editor. I now understand the phrase, “Emacs has taken over my life”.

./screenshots/cover.png

This repo is my version of Emacs:

  • It’s mostly stable but a work in progress
  • It’ll probably always be like that
  • Is very opinionated
  • Is particularly suited to Clojure development
  • Introduces minimal custom shortcuts
  • Is on the evil-side due to objective reasons

Key Features

Project management using Projectile

Any directory with a .git folder is considered as a project. To open a project, just open a file in that directory using Cx Cf. The project will then be cached and accessible via Cc Cp.

./screenshots/screen-projectile.gif

Sidebar using Neotree

Sidebar is bound to f8 key. It is useful while trying to understand the structure of a new project.

./screenshots/neotree.gif

Focus mode using darkroom

Bound to f1, focus mode helps with distraction free writing.

./screenshots/darkroom.gif

Search using Swiper

Swiper is gem bound to Cs. It makes the native search functionality 10x more awesome.

./screenshots/swiper.gif

Opinionated Features

  • Straight.el for package management
  • Powerline
  • Dracula theme
  • Org Journal for notes

Things that can be improved

  • Startup time
  • Documentation

Using this repo

In my early days, Github helped me learn from various public configurations. This config is designed to be barely vanilla. It’s best consumed by readin the source code and taking parts that interest you, or by reading my notes about how I use it.

Notes

The notes are not written in a publication form. You might find occasional typos and incomplete ideas, but should be helpful in general.

Legal

Open sourced under the MIT License. Copyright 2018 Shivek Khurana Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

.emacs.d's People

Contributors

shivekkhurana avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

.emacs.d's Issues

ask hacker news response

I saw your post on Hacker News, linked from Emacs News. I could not find your email. I don't use HN much, Twitter at all, and try to stay away from proprietary software. So, I reply here.

  1. What are some good resources on Emacs?
    The best resources I have found are A) the tutorial (open vanilla Emacs and press enter), B) the manual and C) the Emacs lisp reference. Learn to use the info system inside Emacs. This will help you find the information you need quickly. Also, read the source code for things. Use C-h v and C-h f to quickly look at the source code for whatever you're using.

  2. If you use Emacs as your primary editor, how long did it take you to understand enough internals to be able to debug issues?
    I started by using vanilla Emacs. If a bug appeared, it was always because of something I put in my init. I never put anything I don't (think I) understand in my init. If a problem appears, I know it is likely through something I have done. I remove the code I recently entered and see if the bug goes away. If it does, I isolate the bad part and make sure I can reproduce it. Then, I check my understanding. I have not come across a single Emacs bug in 5 years of daily use. All problems I've had I introduced. In this way, I have more or less always been able to debug issues. It took me reading "An Introduction to Programming in Emacs Lisp" to feel confident extending Emacs, however. https://www.gnu.org/software/emacs/manual/html_node/eintr/index.html

  3. If you use doom/spacemacs, do you feel the bloat?
    I have never used doom/spacemacs because it prevented me from doing the process I described in answer 2.

I do my init a little differently than I've seen others do it. I keep an "experimental.el" file to test code in. Once I feel it's stable, I put it in my init. I use use-package mainly for the syntax and use straight.el to manage my packages (straight.el is great, but not "straight foreward"). This arrangement works well for me. I also have little tricks, like a debug mode for my init which tells me which package just loaded. This helps in the rare cases that I need to bisect my init. I would be happy to do a video chat with you some time. Please let me know, [email protected].

Take care

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.