https://github.com/lionyxml/emacs-kick
A feature rich Emacs (kickstarter) config for (neo)vi(m)mers
https://github.com/lionyxml/emacs-kick
emacs kickstart kickstarter neovim
Last synced: 3 months ago
JSON representation
A feature rich Emacs (kickstarter) config for (neo)vi(m)mers
- Host: GitHub
- URL: https://github.com/lionyxml/emacs-kick
- Owner: LionyxML
- License: gpl-2.0
- Created: 2024-10-03T20:25:32.000Z (over 1 year ago)
- Default Branch: master
- Last Pushed: 2025-10-06T23:02:33.000Z (3 months ago)
- Last Synced: 2025-10-07T01:05:45.193Z (3 months ago)
- Topics: emacs, kickstart, kickstarter, neovim
- Language: Emacs Lisp
- Homepage:
- Size: 3.09 MB
- Stars: 286
- Watchers: 5
- Forks: 12
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
A feature rich Emacs (kickstarter) config for (neo)vi(m)mers
---
# Emacs-Kick(starter) for Vim/Neovim Users
Welcome to `Emacs-Kick`, a feature-rich Emacs configuration designed
for users familiar with `Vim`, `Neovim`, and `Vi`. With this
setup, you don't need to leave behind your favorite terminal or tools
like `yazi`, `starship`, `lazygit`, and `lazydocker` just to
give Emacs a try.
Use Emacs the same way you'd use `Neovim`, seamlessly integrating it
into your workflow inside terminal multiplexers like `tmux` or
`Zellij`, while also enjoying modern features such as `treesitter`
and `LSP`, no hassle.
**Emacs-Kick** isn’t a full-fledged distribution but rather a
**starting point** for building your own Emacs configuration. It’s
designed to be especially accessible for Vim/Neovim users, letting you
explore the power of Emacs without committing to its entire ecosystem.
You can take advantage of Emacs’ features without needing to master
every Emacs-specific workflow right away. And if you find yourself
enjoying it, you can:
- Run it in a GUI for a richer experience
- Customize and expand your configuration as much as you want
- Experiment with frameworks like Doom Emacs or Spacemacs
- Tinker with vanilla Emacs to build a setup entirely your own
OR...
- Just keep using it on TUI, it is all up to you!
With `Emacs-Kick`, the goal is to empower you to explore Emacs at your
own pace. The sky's the limit! 🌟
## Minimum Requirements
- Emacs version **>=30.1**
- You can verify your installed Emacs version by running:
```bash
emacs --version
```
**Note**: floating windows on TUI are only supported from Emacs >=31 (current
development version on Emacs master branch).
### macOS Warning
On macOS, `Emacs-Kick` may fail to function correctly due to missing or
incompatible system utilities. To avoid common issues, make sure the
following tools are installed via Homebrew:
```bash
brew install coreutils git
```
This provides:
- `gls`: The GNU version of `ls`, required by Dired to avoid errors
like:
```
Listing directory failed but 'access-file' worked.
```
- `git`: macOS system usually has an older version of Git, this
typically refers to the version installed through Apple's Command
Line Tools (part of Xcode). Installing from Homebrew ensures a
modern version of git is installed and will avoid problems with
`magit`.
## Installation Instructions
1. **Clone the repository**:
**Note**: If you already have an existing Emacs configuration in
`~/.emacs.d`, please back it up before proceeding. You can do this
by renaming the directory:
```bash
mv ~/.emacs.d ~/.emacs.d.backup
```
If you have any additional configurations from other Emacs
installations, please clean them up. This includes directories and
files such as `~/.emacs.d`, `~/.emacs`, `~/.emacs~`,
`~/.config/emacs`, `~/.config/doom`, `~/.config/cache/emacs` and
any other related files.
After deleting/backing up, clone the repository:
```bash
git clone https://github.com/LionyxML/emacs-kick.git ~/.emacs.d
```
2. **Run the setup**:
After cloning, install the configuration by running:
```bash
emacs -nw --eval="(ek/first-install)"
```
Alternatively, you can run the provided script `ek-reinstall.sh`
from inside `~/.emacs.d/`, which will achieve the same result:
```bash
cd ~/.emacs.d/ && ./ek-reinstall.sh
```
Both methods will install all necessary packages and apply the
configuration.
**NOTE**: During the initial setup, you'll be prompted to install Tree-sitter
grammars and download some fonts. This configuration uses **Nerd Fonts** by
default, so installing them now is highly recommended for the best experience.
**VERY IMPORTANT**: On first launch, Emacs will also **native compile some
external packages**, which may take a little time. Additionally, the first time
you perform certain actions, like opening the tree explorer, Emacs may compile
related components in the background. This is completely normal and only
happens once per feature. You might notice a brief moment of sluggish
performance during this initial compilation.
3. **Set terminal mode by default**:
**Note on Emacs TUI/GUI**: Emacs automatically adapts to either
graphical or terminal mode depending on the environment. But if
you're in a graphical session and prefer terminal mode, just use:
```bash
emacs -nw
```
To ensure Emacs always opens in terminal mode, add the following to
your `.bashrc` or `.zshrc`:
```bash
alias emacs='emacs -nw'
```
Then, reload your shell configuration with:
```bash
source ~/.bashrc # for bash
source ~/.zshrc # for zsh
```
4. **Start Emacs**:
Once set up, start Emacs with:
```bash
emacs
```
**Usage Tips**:
- **Leader Key**: The leader key is set to `SPC` (spacebar),
`which-key` is there to help you discover keybindings.
- **Help Commands**:
- `SPC h i` opens the Emacs info documentation (`M-x info`).
- `SPC h v` allows you to explore available variables.
- `SPC h f` lets you explore functions.
- `SPC h k` displays keybindings.
**Troubleshooting**:
- If you encounter any issues during installation, check the
`*Messages*` buffer for more information. You can switch between
buffers with `SPC SPC`, and navigate options using `C-p` and `C-n`.
## Available Commands
| Keybinding | Action |
| -------------- | ----------------------------------------- |
| `SPC` | Leader key |
| `TAB` | Call completion |
| `C-d` | Scroll down |
| `C-u` | Scroll up |
| ` s f` | Find file |
| ` s g` | Grep |
| ` s G` | Git grep |
| ` s r` | Ripgrep |
| ` s h` | Consult info |
| ` /` | Consult line |
| ` x x` | Consult Flymake |
| `] d` | Next Flymake error |
| `[ d` | Previous Flymake error |
| ` x d` | Dired |
| ` x j` | Dired jump |
| ` x f` | Find file |
| `] c` | Next diff hunk |
| `[ c` | Previous diff hunk |
| ` e e` | Toggle NeoTree |
| ` g g` | Open Magit status |
| ` g l` | Show current log |
| ` g d` | Show diff for current file |
| ` g D` | Show diff for hunk |
| ` g b` | Annotate buffer with version control info |
| `] b` | Switch to next buffer |
| `[ b` | Switch to previous buffer |
| ` b i` | Consult buffer list |
| ` b b` | Open Ibuffer |
| ` b d` | Kill current buffer |
| ` b k` | Kill current buffer |
| ` b x` | Kill current buffer |
| ` b s` | Save buffer |
| ` b l` | Consult buffer |
| `SPC` | Consult buffer |
| ` p b` | Consult project buffer |
| ` p p` | Switch project |
| ` p f` | Find file in project |
| ` p g` | Find regexp in project |
| ` p k` | Kill project buffers |
| ` p D` | Dired for project |
| `P` | Yank from kill ring |
| ` P` | Yank from kill ring |
| ` .` | Embark act |
| ` u` | Undo tree visualize |
| ` h m` | Describe current mode |
| ` h f` | Describe function |
| ` h v` | Describe variable |
| ` h k` | Describe key |
| `] t` | Go to next tab |
| `[ t` | Go to previous tab |
| ` m p` | Format with Prettier |
| ` c a` | Execute code action |
| ` r n` | Rename symbol |
| `gI` | Find implementation |
| ` l f` | Format buffer via LSP |
| `K` | Show hover documentation |
| `gcc` | Comment/uncomment current line |
| `gc` | Comment/uncomment selected region |
| `gd` | Goto definitions |
| `gr` | Goto references |
...and a lot more, discoverable with which-key :)
## Contributing
This package is intentionally designed with a specific vision in mind,
reflecting my own opinions and preferences. While contributions are
welcome, please understand that this configuration is quite
opinionated.
If you have suggestions or requests, they will be considered
carefully, but I cannot make any promises regarding implementation or
acceptance. Your input is valuable, and I appreciate any help or
feedback to improve the project.
To contribute, feel free to open an issue or submit a pull
request. Let's make this configuration even better together!
## About PRs
Always welcome, not a promise to accept though (see above). Please
direct your PRs to the `development` branch of this repository.