use-package VS consult

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.

BTW, as an alternative to swiper, you can check out consult-line and related commands from consult.

Consult is what you are looking for: https://github.com/minad/consult In particular try consult-ripgrep

Emacs has code peek.

With lsp-mode it has that little window: https://emacs-lsp.github.io/lsp-ui/#lsp-ui-peek

Personally I use eglot with consult which temporarily switches the entire buffer to do the "peek" functionality rather than popping up a tiny window: https://github.com/minad/consult

Thanks for working on this! I just added a consult--maybe-recenter function in a recent commit. This is a nice idea since it can reduce the jumpiness of Consult preview quite a bit.

An example relevant to your list would be some changes many people are taking with their completion framework - using package that leverage core emacs functionality rather than replacing it with a complete package that 'overrides' it. Consult, vertico, orderless and associate packages come to mind here. If you do a bit of a search you'll find plenty of info. Here is a video from Prot on the subject, but there are many others as well. I think Prot actually went on to write his own completion system to overlay native emacs functionality as well.

For the "lauch workspaces", I use burly which just uses simple bookmarks. Then with consult, I just use C-x b, then m to narrow to bookmarks and I have all the workspaces available (remote as well).

Debugger entered--Lisp error: (error "Invalid face" bookmark-menu-heading) internal-set-lisp-face-attribute(bookmark-menu-heading :family unspecified 0) set-face-attribute(bookmark-menu-heading nil :foreground unspecified :background unspecified :family unspecified :slant unspecified :weight unspecified :height unspecified :underline unspecified :overline unspecified :box unspecified :inherit nano-face-strong) set-face(bookmark-menu-heading nano-face-strong) #() eval-after-load-helper("/usr/local/share/emacs/29.0.90/lisp/bookmark.elc") run-hook-with-args(eval-after-load-helper "/usr/local/share/emacs/29.0.90/lisp/bookmark.elc") do-after-load-evaluation("/usr/local/share/emacs/29.0.90/lisp/bookmark.elc") require(bookmark) byte-code("\300\301!\210\300\302!\210\303\304\305\306\307\310\307\311\307\312\313\314\313\315\313\316\317\320&\21\210\321\322\323\324\325DD\326\327\330%\210\321\331\323\324\332DD\333\327..." [require compat bookmark custom-declare-group consult nil "Consulting `completing-read'." :link (info-link :tag "Info Manual" "(consult)") (url-link :tag "Homepage" "https://github.com/minad/consult") (emacs-library-link :tag "Library Source" "consult.el") :group files outlines minibuffer :prefix "consult-" custom-declare-variable consult-narrow-key funcall function #f(compiled-function () #) "Prefix key for narrowing during completion.\n\nGood ..." :type (choice key (const nil)) consult-widen-key #f(compiled-function () #) "Key used for widening during completion.\n\nIf this ..." (choice key (const nil)) consult-project-function #f(compiled-function () #) "Function which returns project root directory.\nThe..." (choice function (const nil)) consult-async-refresh-delay #f(compiled-function () #) "Refreshing delay of the completion UI for asynchro..." float consult-async-input-throttle #f(compiled-function () #) "Input throttle for asynchronous commands.\n\nThe asy..." consult-async-input-debounce #f(compiled-function () #) "Input debounce for asynchronous commands.\n\nThe asy..." consult-async-min-input #f(compiled-function () #) "Minimum number of letters needed, before asynchron..." natnum consult-async-split-style #f(compiled-function () #) "Async splitting style, see `consult-async-split-st..." ...] 18) require(consult) byte-code("\300\301!\210\302\303\304\305#\210\306\211\203,\0\211@\303\1N\203%\0\304\1N\204%\0\307\304\2\303\4N#\210\1A\266\202\202\13\0\210\310\303\304\311#..." [require consult defvaralias consult-notes-sources consult-notes-file-dir-sources nil (saved-value saved-variable-comment) put make-obsolete-variable "0.6" consult-notes--all-sources consult-notes-all-sources custom-declare-group consult-notes "Search notes with consult." :group convenience custom-declare-variable consult-notes-category funcall function #f(compiled-function () #) "Category symbol for the notes in this package." :type symbol #f(compiled-function () #) "Sources for `consult-notes'." (repeat symbol) #f(compiled-function () #) "Directories of files for searching with `consult-n..." (list string key string) consult-notes-file-dir-annotate-function #f(compiled-function () #) "Function to call for annotations of file note dire..." consult-notes-use-rg #f(compiled-function () #) "Whether to use ripgrep or just grep for text searc..." boolean consult-notes-ripgrep-args #f(compiled-function () #) "Arguments for `ripgrep' and `consult-notes-search-..." string consult-notes-grep-args #f(compiled-function () #) "Arguments for `grep' and `consult-notes-search-in-..." consult-notes-default-format #f(compiled-function () #) "Default format for `consult-notes' open function." sexp consult-notes-max-relative-age ...] 8) (consult-notes-org-headings-mode) eval-buffer() ; Reading at buffer position 2730 funcall-interactively(eval-buffer) call-interactively(eval-buffer record nil) command-execute(eval-buffer record) execute-extended-command(nil "eval-buffer" "eval-bu") funcall-interactively(execute-extended-command nil "eval-buffer" "eval-bu") call-interactively(execute-extended-command nil nil) command-execute(execute-extended-command)

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

They're still coming in. This one is from yesterday: https://github.com/minad/consult/issues/793

If you like meow-visit also try imenu it is built into Emacs and can be very useful either by itself or as part of consult. consult also has a consult-mark function that can be helpful, meow kind of breaks it since it makes a lot of marks.