configuration VS consult

FWIW I have this little Perl script that fetches BibTeX from doi.org for DOI numbers: https://github.com/cadadr/configuration/blob/76466b1342aaadfddf3453ab70ada4a15e82afbb/bin/doi2bib.pl I searched a lot for a way to make something similar for ISBN -> BibTeX to no avail...

If you're writing LaTeX without using any supporting software, it will be harder. But there are some things that you can use to make life way easier. One of these is the concept of "snippets". In Emacs I use something called yasnippet, and it works like this: I define a snippet like this or even something more elaborate like this. They have "trigger words". E.g. for the second one, I type "report" in a file and hit TAB. It inserts all that "snippet" to the file, and I can edit parts marked as $1, $2 and similar, jumping between them using TAB. I use this with Org mode, which is like Markdown, so it's not much different from typing into Word, essentially. There's some initial work figuring out how to do something like a syntax tree or say an equation, but once you figure a pattern out you can make it into a template using snippets and it's easier than Word once you have that.

There are some examples in my init.el, you can find them if you search for :after.

The way I do python is, I've a proxy shell script which I set as the python interpreter in Emacs.

One particular thing I can suggest for equations is dynamic latex equation previews, which toggles TeX source when the cursor is on an equation but when it goes out of it it toggles a rendered preview. See this and this, adapted from this).

Wrt LSP specifically, I only use it with python and the whole config is this couple lines plus this hook. IDK how lsp-mode is configured but this works fairly well for me, and actual Python config is a bit more cumbersome (because Microsoft comes up with a new Python LSP package every other day and you can't know which one to deal with...). It hooks into Emacs' complete-symbol (i.e. C-M-i), so if company or whatever (sorry, I don't really know those packages well, there was auto-something too but IDK which one is better or recommended these days) does use that mechanism as a backend, it should work seamlessly. I've made these little bindings to quickly pick a completion from the *Completions* window (gk-interactively is just a macro that expands to (lambda () ). Again, eglot hooks into Emacs' completion mechanism, so I'd risk a guess that helm or ivy would just work with that. Personally I don't like these completion frameworks because again they look to me like they are somewhat useful but not enough to warrant their complexity. I like good old completing-read, with some modern configuration (and BTW the UI Semantics section that bit is in in my init.el contains a lot of what you could call "saner defaults"). Notably they've added some very neat structural and fuzzy matching abilities starting with 25.1 IIRC and I don't even feel the need to turn ido on when those features are enabled.

I have a little project system that I use a lot and is a life saver: https://github.com/cadadr/configuration/tree/3e11ef25344188cc55b16f314c3c5358ace8a266/emacs.d/init.el#L1249 It's simple but it's very helpful. I like to have a project command view with dired at root on the left and magit or vc.el on the right, and I can go back to that view with a single command, gk-home, bound to the Home key. Popping a shell at bottom like yakuake with a single keybinding to gk-pop-shell is very useful too. I use frame parameters to tie projects up with frames so these two functions know what to do in each project frame. Titles are set up such that it's easy to find a particular frame with something like Rofi.

Depends on what you want to do. Linux is a more welcoming environment for programmers and an OS-level package manager is very helpful. I have one big repo for all my configs, and if my computer failed today I can get up and running on anything else in a couple hours, typing a few commands only. With Windows it's always a manual process and takes longer. And sometimes Windows makes some programmers' tasks too hard, like setting environment variables, etc. And more advanced things like scripting, virtualisation, containers, etc. are generally easier to do in Linux.

E.g. a very important detail IMHO is the active vs. inactive modelines. In your light theme they are virtually the same, so you need to chase the cursor to find the active window. The first thing I modify in themes I use is to make modeline colours such that inactive one is faded but still legible, and active modeline really stands out: https://github.com/cadadr/configuration/blob/bf8b87c36dbab85d1ec35f3c9aa6f7d3c5e1f347/emacs.d/init.el#L5842 In general if you're not limited by a palette it's easier to adjust everything perfectly.

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.