consult VS magit

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.

Then the slowness that you're seeing is probably Windows-specific, and that's why everyone else is telling you that Magit is actually fast.

WSL might make things faster.[1] IIUC, the problem is that starting new processes is much slower on Windows than on Linux/Unix and Magit relies heavily on that. This seems to have plagued Git tooling more generally but maybe this got fixed since then.[2]

[1] https://emacs.stackexchange.com/a/58444

[2] https://github.com/magit/magit/issues/2395#issuecomment-1710...

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

> Even in this article just a few sentences after stating we should start from first principles he then jumps into the assumption of the "desktop".

Agree. Although I can see how the idea of "first principles" can be a very difficult starting point. A blank sheet of paper is a scary monster.

There's a huge breadth and depth of non-"desktop" GUIs out there, some (like smartphones) are even wildly successful. It's good to explore them for inspiration. Some of my favourites:

- Arcan (https://arcan-fe.com/about/) - I won't attempt to summarize, just dive in!

- SailfishOS (https://sailfishos.org/) - mobile UI focused on interaction through gestures / swipes; I've used it as my daily driver for a couple years.

- Speaking of mobiles, classic Nokia UIs allowed you to navigate to a specific item in the menu by pressing the corresponding digit on the dial pad. Once you learned where a particular item is, accessing e.g. your SMS inbox was extremely quick.

- Apple Watch / WatchOS (https://www.apple.com/watchos/) - I've always loved the idea of a device where one of the primary interaction methods was a wheel/dial of some sort. The watch even gives you context-sensitive tactile feedback.

- ZUIs in general (https://en.wikipedia.org/wiki/Zooming_user_interface) and the work of Jef Raskin in particular: https://en.wikipedia.org/wiki/Archy_(software) - this is the guy who helped design the Macintosh, but his other work took a radically different route.

- Magit (https://magit.vc/). Many common git operations are reduced to a couple of keystrokes; the obscure features are more discoverable, and the cumbersome procedures (such as rebasing, or staging individual hunks) become simple and intuitive. Also check out transient (https://github.com/magit/transient), which is the "UI toolkit" that powers Magit.

This can be done most comfortably with org-mode in emacs. It offers a lot of features, and they all operate on plain text. There are also nice integrations for git and languagetool, but I guess those are less exclusive.

How does this differ from https://magit.vc/ ?

I would rather see innovative tools that lessen our dependency on 50+ year old tech. This is still a glorified teletype. It uses AI to autosuggest git commands? Contrast with Magit[1], which (while it has a tiny bit of a learning curve, but also nowhere near 23M in funding) actually makes interacting with git a pleasure.

[1]: https://magit.vc

Also was using Emacs (org-mode)[https://orgmode.org] for years with (Magit)[https://magit.vc] package for git. I feel org-mod is a precursor to Roam Research, Obsidian, et al. Hit the spot for years but I wanted editing on mobile so that’s why I’m here. :)