emfy
vim-which-key
emfy | vim-which-key | |
---|---|---|
18 | 25 | |
929 | 1,902 | |
- | - | |
5.9 | 6.0 | |
5 months ago | 4 months ago | |
Emacs Lisp | Vim Script | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
emfy
- Emacs for You (Emfy): Tiny init.el for beginners to quickly set up vanilla Emacs
-
Should I start with vanilla Emacs?
Vanilla. A good starting point for you is probably Emfy - https://github.com/susam/emfy
-
Making Emacs more approachable
I recommend Susam Pal's attempt to make Emacs more approachable for beginners: https://github.com/susam/emfy. He provides a line-by-line explanation of a simple config file.
- How to progress from beginner level
-
Helix: Post-Modern Text Editor
That is true. But it’s pretty overwhelming for a lot of folks. I was a spacemacs user. I tried to rebuild what I liked about it. It was a lot, and I didn’t quite get it there.
I finally found a good compromise though. I started over with this confing: https://github.com/susam/emfy
From there, I only needed a handful of packages and a few dozen lines of config to get to an editor that was comfy.
-
VS Code – What's the deal with the telemetry?
I struggled to make the change. I think I tried half a dozen times to go from (neo)vim to Emacs and it never stuck. My problem was that I kept reaching for spacemacs and Doom Emacs, etc., right out of the gate, and I would be mystified by Emacs itself and Emacs Lisp as a result.
Two things helped get me into Emacs full-time (and this is after > 15 years of using vim):
1. I went step-by-step through Susam's Emfy Emacs config [0]. That helped me understand some of the basics at a foundational level. I extended that base configuration a little bit and became comfortable with the environment.
2. I then went step-by-step through the entire "Emacs from Scratch" playlist that System Crafters put out [1]. I pushed my personal configuration pretty far with that over the course of 2-3 months.
I eventually moved to Doom Emacs and married in pieces of my own configuration. That's been my daily driver for months now.
[0]: https://github.com/susam/emfy
[1]: https://www.youtube.com/playlist?list=PLEoMzSkcN8oPH1au7H6B7...
- Moving from Doom to Vanilla
-
Ask HN: Should I learn Emacs in 2022?
Just have a weekend learning Emacs + Lisp and make your own opinion. This configuration (https://github.com/susam/emfy) is a great start. If you like it - use it, if you don't - throw it away.
-
Packages for Emacs beginner
Rather than one of the fat and opinionated "distros" (doom, spacemacs) I like emacs for you. It will set you up with a minimal config that you can learn from and add to as you go.
vim-which-key
-
Vim distros: LunarVim, AstroVim, IdeaVim, … how they differ one each other?
The only Vim distro I'm aware of is SpaceVim (https://spacevim.org/). I just tested it for a short time but it couldn't compete with my hand crafted settings ;-) But I'm using some of the plugins of SpaceVim in my setup, eg. vim-which-key and vista.vim.
-
plugins for explorable interface and identifier highlighting
Sounds like you want vim-which-key and coc.nvim.
-
Tell HN: Vim users, `:x` is like `:wq` but writes only when changes are made
> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.
CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:
A couple of nice examples of discoverability in keyboard-focused programs:
- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.
- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.
[0] https://github.com/justbur/emacs-which-key
[1] https://github.com/liuchengxu/vim-which-key
[2] https://magit.vc/
[3] https://emacsair.me/2017/09/01/magit-walk-through/
- Is there a way to get a cheatsheet on-screen like nano has?
-
A Vim Guide for Advanced Users
Agreed, that's the only time I find missing Emacs' which-key. (Looks like there is https://github.com/liuchengxu/vim-which-key for this.)
-
Navigate through options of Plugins
I think you mean a plugin which shows available key bindings as you type, which is what vim-which-key does.
-
Helix: Post-Modern Text Editor
Just an extension.
It is https://github.com/liuchengxu/vim-which-key if you are interested.
>Were you also able to replicate the small popups that open when you press `m`, `g`, etc.?
Yes, although 'm' has a totally different meaning in vim (placing a mark), so there is no popup for that. But it works where there are actually sensible choices, even for marks it works and shows you every available one, which is pretty cool
-
Vim, infamous for its steep learning curve, often leaves new users confused where to start. Today is the 10th anniversary of the infamous "How do I exit Vim" question, which made news when it first hit 1 million views.
But again, that's not a specifically vim issue, its endemic to TUIs (hence bash completions and all the other hacks to make discoverability accesible). As well, there are some projects to ameliorate this in vim like the which-key family of plugins01 and others like them.
-
Is my understanding of Vim and Emacs correct?
__usability features__ Emacs has a lot of great ideas for usability, some of which have been copied to vim like which-key https://github.com/folke/which-key.nvim https://github.com/liuchengxu/vim-which-key
-
What is the biggest barrier of entry for learning vim?
Printing cheat sheets is helpful. At some point, make your own. which-key.nvim (or vim-which-key) is a plugin I wish I had found years ago. It gives you hints of next keys available to press. It's great for beginners, and experts. It's like the ultimate real-time cheatsheet.
What are some alternatives?
emacs_python_ide - Settings to make emacs a python-ide
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.
quarto-emacs - An emacs mode for quarto: https://quarto.org
bufferline.nvim - A snazzy bufferline for Neovim
logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
tokyo-night-vscode-theme - A clean, dark Visual Studio Code theme that celebrates the lights of Downtown Tokyo at night.
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
emacs-which-key - Emacs package that displays available keybindings in popup
jake-emacs - My personal Emacs configuation.
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
helix-vim - A Vim-like configuration for Helix
vim-rsi - rsi.vim: Readline style insertion