evil-guide
use-package
evil-guide | use-package | |
---|---|---|
15 | 67 | |
1,227 | 4,370 | |
- | - | |
0.0 | 2.3 | |
about 2 years ago | 3 months ago | |
Emacs Lisp | ||
GNU General Public License v3.0 only | 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.
evil-guide
-
Emacs Bedrock–A minimal Emacs starter kit
2. the leader key https://github.com/noctuid/evil-guide#leader-key
these are random search results that may or may not be authoritative, but they should be a good start.
-
How do I change the Vim settings inside of Doom Emacs?
Doom uses Evil-mode for vim emulation. https://github.com/noctuid/evil-guide is a good guide for translating between vim concepts and Emacs.
- Emacs <==> vi/vim "Rosetta Stone"?
-
Intro to Evil for non-Vim users? Beyond evil-tutor
I'm not aware of a guide specifically for non-vim users, but pretty much any vim guide will be helpful - it's just best to avoid parts on vimscript, as evil isn't configured using that. Even though it introduces itself as a guide for Vim users, I still think https://github.com/noctuid/evil-guide is worth a read. As for packages which complement evil, most are named with evil as a prefix, so you can browse melpa with that in mind. One exception that comes to mind is lispyville, which provides an evil approach for editing s-expressions. evil-cleverparens is also worth a look. Feel free to ask any questions on the evil issues page too!
-
About to declare Emacs bankruptcy. Any advice for cool or new packages, defaults, or ideas I should use before I start building my init.el? Also interested in guides to using evil.
Evil is a complex machinery build by vim nostalgic refugees, so familiarity with Vim's modal editing model is still recommended. I like this, even if it's not a tutorial: https://github.com/noctuid/evil-guide
-
How to actually define key binds in Emacs?
I'd recommend reading noctuid's evil guide, particularly the link to the spacemacs keymap guide and the mention of the commentary on evil-core.el
-
Is it worth renouncing evil and becoming a good person?
It’s probably worth understanding what evil is doing so you can make your own key bindings for packages you find. I personally don’t think evil is obscuring things for me because I’ve gotten pretty good at using the introspection features of emacs to look at what everything is doing. The guide from noctuid was a good reference when I read it https://github.com/noctuid/evil-guide.
-
Consistent Emacs Keybindings
Set aside a little bit of time to learn properly how Emacs and evil-mode work together. Not sure if you've seen it, but here's an excellent guide for transitioning from Vim to Emacs with evil-mode. It's by the author/maintainer of general.el.
-
Is there a way to present a warning message when a key combination is redefined? So I have some kind of heads up that a conflict occured?
A bit unrelated to your question, but if you are having trouble with keybindings I really recommend this read. Also, if you use evil-mode, reading evil-guide is really worth it as well, to understand how to configure things correctly.
-
Is there a package to use Vimscript in evil-mode?
This should make the porting process easier https://github.com/noctuid/evil-guide
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?
nano-emacs - GNU Emacs / N Λ N O - Emacs made simple
leaf.el - Flexible, declarative, and modern init.el package configuration
expand-region.el - Emacs extension to increase selected region by semantic units.
straight.el - 🍀 Next-generation, purely functional package manager for the Emacs hacker.
avy - Jump to things in Emacs tree-style
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
olivetti - Emacs minor mode to automatically balance window margins
elegant-emacs - A very minimal but elegant emacs (I think)
org-super-agenda - Supercharge your Org daily/weekly agenda by grouping items
transient - Transient commands
melpa - Recipes and build machinery for the biggest Emacs package repo