emfy
vis
emfy | vis | |
---|---|---|
18 | 56 | |
929 | 4,172 | |
- | - | |
5.9 | 8.2 | |
5 months ago | 4 days ago | |
Emacs Lisp | C | |
MIT License | GNU General Public License v3.0 or later |
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.
vis
- Vis: A vi-like editor based on Plan 9's structural regular expressions
- Oasis – a small, statically-linked Linux system
-
Why Kakoune
> I wonder if the author has ever heard of vis[0]
Yes.
https://github.com/martanne/vis/wiki/Differences-from-Kakoun...
https://github.com/mawww/kakoune/wiki#onboarding
> which imho fulfills far better each one of those premises
Not very motivated for such a harsh critic..
-
The Text Editor Sam by Rob Pike
If you want an editor that uses Sam's structural regexes with keyboard-focussed vi-style interaction, you might be interested in https://github.com/martanne/vis
-
Can we write a Neo-vim Successor using rust?
Not Rust, but there's vis which aims to be a Vi(m) inspired editor with Sam's structural regular expressions.
-
Met that guy one the train yesterday
I do not use vim nor a WM nor a Thinkpad, but I do use vis. It's great.
-
Helix: Release 23.03 Highlights
> They either break from Vim's model (kakoune, helix) or follow Vim along with all it's flaws (Neovim, Vis).
I am sincerely curious of what flaws from Vim has Vis inherited, in your opinion.
I have the impression that the design idea of Vis is taking only the modal design of Vi (not Vim), plus the structural regular expressions of Sam, then make it as clean as possible with programmability via Lua plugins.
In fact, the state non-goals [1] seems to clearly distant itself from Vim.
[1]: https://github.com/martanne/vis#non-goals
- Helix: Post-Modern Text Editor
- Mle is a small, flexible, terminal-based text editor written in C
What are some alternatives?
emacs_python_ide - Settings to make emacs a python-ide
kakoune - mawww's experiment for a better code editor
quarto-emacs - An emacs mode for quarto: https://quarto.org
micro-editor - A modern and intuitive terminal-based text editor
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.
nextvi - Next version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
vim-visual-multi - Multiple cursors plugin for vim/neovim
jake-emacs - My personal Emacs configuation.
mle - flexible terminal-based text editor (C)
helix-vim - A Vim-like configuration for Helix
nvim-select-multi-line - Neovim plugin. select multiple lines that are not adjacent.