objed VS use-package

To build on what others are saying about Emacs, if you start exploring the package ecosystem, you're going to see quite a lot of really interesting packages that are related to improving/experimenting with the UX of editing text. While I'm not endorsing anyone in particular, I think what this list does show is just how easy it is to do pretty much whatever you want in Emacs;

https://karthinks.com/software/avy-can-do-anything/

https://github.com/jyp/boon

https://github.com/clemera/objed

https://github.com/jmorag/kakoune.el

https://github.com/meow-edit/meow/

https://github.com/xahlee/xah-fly-keys

https://github.com/Kungsgeten/ryo-modal

https://github.com/emacsorphanage/god-mode

Emacs 29 also now has treesitter and LSP mode integration built-in, a compilation mode, a comint mode for REPLs, excellent file browsing packages (I use dired/dirvish), and a few other killer features.

Now, if what you truly dislike are "quirky editors", prepare yourself for a world of hurt because vanilla Emacs departs quite a bit from "modern" text editors. I struggled with this for a while, but eventually by buying into the paradigm, I now feel that when emacs try emulating "modern" IDE features like autocompletion, LSP, and DAP UI, I feel like it's a regression, not a progression. The point here is that you might have an "idea" of what good initial UX and lack of quirks would look like, but Emacs might change the way you think.

This looks like an interesting and valiant attempt to build something that improves on everything that came before it, but I did find the documentation lacking in clarity.

I'm experimenting with this package right now instead:

https://github.com/clemera/objed

and will wire up the keyboard shortcuts using RYO package to roll my own modal state.

3.objed:: https://github.com/clemera/objed.git

Wow. meow project looks similar to objed but with more features. These projects are inclined to modal editing but not being vim. Thank you for suggesting.

I like the semi-modal editing package objed (short for textual object editor)

This reminds me of u/clemera's objed and of versor.

There are other modal systems for emacs. You even can construct your own with https://github.com/mrkkrp/modalka and https://github.com/Kungsgeten/ryo-modal. I have done that, these packages were extremely easy to use. I had a lot of fun designing the modal regime of my dreams. There are https://github.com/LouisKottmann/emacs-baboon, https://github.com/xahlee/xah-fly-keys (and its various forks) and https://github.com/clemera/objed.

I forgot about objed! Which is another very interesting project.

I didn't fully get what your interactive piping solution is, but I found that objed has a command oddly unrelated to the rest of its codebase: objed-ipipe, which does what I imagined Howard's piper to do but more intuitively to me. Though it seems you can write piper commands out in lisp so it's probably a superset feature-wise, I just never got started learning it.

Well laid out, I fully agree. I think there is still a lot of potential to combine these two approaches in a better way, Emacs knows about many structures already but I think it could be more convenient to act on those. I tried my hand on this with objed which aims to make it easier to act/navigate on certain units (on demand or semi automatically).

Another way would be to redefine parts of the bind-key macro or its use-package support functions

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.

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.

> 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

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).

I'm using use-package as my package manager and the package ligature for the ligatures.

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.

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.