After spending a bit of time learning Emacs, I’ve found it has a widespread compatibility with a lot of the basic movement and editing commands. Spending a bit of time learning these commands can make you more effective in a variety of places, even if you don’t use Emacs as your preferred editor. Read more on 12 Emacs Keybindings Worth Learning…
I spend a lot of my day working on the command line, from file navigation to version control to remote work on servers over SSH, and anywhere in between. I’ve found that even small improvements to my workflow significantly add up over time to provide big productivity boosts.
Read more on Improving Command Line Productivity with GNU Readline…
For almost a year now, I have been using Spacemacs, an Emacs distribution designed to make Vim users and newcomers to Emacs comfortable in Emacs, as my daily text editor. I was initially hooked by the nearly flawless Vim emulation, which is the best I have used in any text editor. After I had gotten my feet wet, I fell in love with the pre-defined mnemonic shortcuts and amazing packages that are included in the distribution.
Read more on Three Awesome Spacemacs Features…
I’ve recently been doing some basic Clojure development, and it’s been a huge blast. I’ve played around with it in the past, but never bothered to fully set up a development environment. This time, however, I decided to spend a few evenings perfecting my workflow and becoming familiar with the tools available, focusing on my editor of choice: Spacemacs.
Read more on Clojure Development in Spacemacs…
I knew it was possible to do what I wanted from within Emacs, as evidenced by other test runner modes like RSpec-mode. Armed with that knowledge, I decided to go through the process of learning enough Emacs Lisp to make a Mocha test runner. In the process, I learned a lot about developing Emacs packages and ended up with a really useful tool, so I thought I would share some of the things I learned.
Read more on Take Your Emacs to the Next Level by Writing Custom Packages…
Atomic Object has a great tradition of making and customizing tools. It’s a habit I’ve gained and lost several times over my career — keeping tools sharp requires time and effort. Fortunately, one of the best things about becoming an Atom is that all of my colleagues care deeply about software, so it’s easy to find inspiration to start making tools again.
I love Emacs. I’ll take it hands down over vim, Sublime, Atom, and company any day. I thought I would take some time to list some of my favorite bits of Emacs and how I use them in my daily workflow.
Magit is an Emacs interface for git. Beyond that, it’s the best interface for git I have ever used — better than the git CLI or third-party apps like SourceTree. Magit reduces most git commands (and all of their cryptic flags) to a series of one-character shortcuts. It also introduces interactive status and log buffers that are comparable to any other git gui out there (and better than many). The best part is that version control becomes part of my editing workflow and requires no context switching. Overall I find that it massively speeds up and simplifies my git workflow and encourages me to use my VCS to its fullest extent. Read more on My Favorite Emacs Add-Ons…
I am an avid Emacs enthusiast in a company full of Vim users. In fact so many people I work with like to use Vim that they even created a company wide Vim config for everyone to use. This has presented a problem to me: Emacs or Vim? On the one hand, I absolutely love Emacs and have invested significant time into customizing it to work exactly the way I want. But on the other hand, I want to be on board with the tools everyone I work with is using.
Is the solution here to just accept the fact that Vim is an excellent text editor too, and adopt it for my work? No way!
The Evil Solution
Instead, I decided to just to port Atomic’s Vim config into Emacs and use both editors at the same time. Fortunately for me, someone has already done most of the work for me by creating Evil, the Extensible vi layer for Emacs.
Ever find yourself at the Bash prompt, typing out a very long series of arguments or parameters, only to hideously misspell something at the beginning on the line?
If you’re handy with the emacs editor, you already know the answer. You can use the emacs key bindings to go back and efficiently edit your command line. You don’t need to retype it, or tediously use the arrow keys to go back character-by-character.
However, what if you’re not handy with emacs bindings, but vi bindings? What then?