emfy
use-package
emfy | use-package | |
---|---|---|
18 | 67 | |
929 | 4,369 | |
- | - | |
5.9 | 2.3 | |
5 months ago | 3 months ago | |
Emacs Lisp | Emacs Lisp | |
MIT License | GNU General Public License v3.0 only |
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.
use-package
-
Use-Package & different key bindings based on host computer
Another way would be to redefine parts of the bind-key macro or its use-package support functions
-
Can't remove Emacs as "cask emacs is not installed"
The package-install call installs use-package that provides a utility of the same name to make it easier to manage packages. It's admittedly a little overkill for this specific config, but it's a cheap investment that sets you up for later success.
-
symbols function definition is void: map!
Granted, the Doom macro makes your code looks nice and compact. But you can get very close to that just by using do-list and define-key together. Or by using the bind-key.el package, which is included with Use-package.
- 'org' is already installed (use-package)
-
Clojure Turns 15 panel discussion video
> Deps is well documented.
> The issue I personally found is that I needed to look at a bunch of OS project's deps.edn to see how people commonly structure things. Other than that it is a simple tool.
This strikes me as a contradiction, because if it was well documented you wouldn’t need to look at other people’s configs to see how to use it.
My experience with deps.edn is that every time I start a project and make a deps.edn file, I immediately draw a blank and don’t know how to structure it, so I open ones from other projects to start lifting stuff out of them.
I still don’t know how to reliably configure a project to use nrepl or socket repl without just using an editor plugin. I definitely have no idea how to use those in conjunction with a tool like reveal.
To me, none of that is simple. Simple would be like Emacs’ use-package. With that I know how to add dependencies, specify keybinds, and do initialization and configuration off the top of my head. And it has really nice documentation with tons of examples.
https://github.com/jwiegley/use-package
-
Newbie here! Need Help!
Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).
-
Unable to display ligatures in Emacs
I'm using use-package as my package manager and the package ligature for the ligatures.
-
Boilerplate config
I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.
-
what is basic alghoritm/logic of installation packages to emacs?
ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package
-
Visual code folding?
use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.
What are some alternatives?
emacs_python_ide - Settings to make emacs a python-ide
leaf.el - Flexible, declarative, and modern init.el package configuration
quarto-emacs - An emacs mode for quarto: https://quarto.org
straight.el - 🍀 Next-generation, purely functional package manager for the Emacs hacker.
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.
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
nano-emacs - GNU Emacs / N Λ N O - Emacs made simple
jake-emacs - My personal Emacs configuation.
org-super-agenda - Supercharge your Org daily/weekly agenda by grouping items
helix-vim - A Vim-like configuration for Helix
melpa - Recipes and build machinery for the biggest Emacs package repo