#
evil-mode
Here are 36 public repositories matching this topic...
good first issue
Good for newcomers
precision Lisp editing with Evil and Lispy
-
Updated
May 2, 2019 - Emacs Lisp
Evil Swift code. Because I can.
-
Updated
Jan 23, 2021 - Swift
Make Emacs drop lazily repeated "hjkl"-based motions after a configurable threshold
-
Updated
Aug 7, 2021 - Emacs Lisp
My Emacs Config
-
Updated
Oct 17, 2021 - Emacs Lisp
-
Updated
May 24, 2020 - Emacs Lisp
A modern(?) day Emacs configuration for the stubborn dvorak vimmer
-
Updated
Aug 2, 2021 - Emacs Lisp
A Simple, Fully Featured, and EVIL (Extensible VI Layer) Emacs Config
-
Updated
Dec 27, 2021 - Emacs Lisp
Make Emacs an easy to use Text Editor for English and Chinese on macOS.
vim
macos
emacs
evil
emacs-configuration
text-editor
literate-programming
org-mode
org-mode-configuration
evil-mode
emacs-vim
-
Updated
May 18, 2022 - Org
This is a personal (and Evil) awesome 😎 list of development tools, resources, platforms, inspiration. All the content is curated and verified as awesome by this humble developer.
-
Updated
Jan 5, 2019
This repository consists of my emacs configuration
emacs
forge
emacs-lisp
melpa
hydra
magit
ivy
org-mode
projectile
elpa
use-package
evil-mode
helpful
org-babel
counsel
emac-configuration
autopair
counsel-osx-app
-
Updated
Dec 17, 2020 - Emacs Lisp
My config files
-
Updated
May 14, 2021 - Emacs Lisp
Some of my DotFiles
-
Updated
Oct 18, 2020 - Shell
My personal emacs settings
-
Updated
Aug 18, 2017 - Emacs Lisp
Active emacs configuration
-
Updated
Feb 22, 2022 - Emacs Lisp
My config repository for Doom Emacs, the most versatile text editor in the world.
-
Updated
Aug 8, 2021 - Emacs Lisp
Improve this page
Add a description, image, and links to the evil-mode topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the evil-mode topic, visit your repo's landing page and select "manage topics."


(Elisp)-tree-sitter represents sections of the code it cannot parse as
ERRORsymbol tokens. Currently the parser will fail as if a transformation is invalid if anyERRORtokens are present. Instead, we should check if the tokens in an operation containERROR, and alert the user that their code is malformed if so.