7890yuiop

Assuming that you are referring to plain text...

while keeping them as clickable links

First of all you need to establish why a plain text URL is doing something when you click on it, as your new requirement is going to need to interact with that.

(I'm guessing goto-address-mode is enabled, so I would check that first.)

• Updates Magit and Transient
• Plays with C-x a in Magit's menus
• Very nice! I love that it highlights the changes. Thanks!

• They used to be hard to remove. As mentioned, M-x remove-hook has alleviated that to an extent.
• They are still harder to update because you need to remember to remove the old one when adding the replacement. I've seen any number of cases where people were inadvertently adding lots of slightly different versions of their function to a hook variable, and wondering why they were still having problems.
• They are very unhelpful when you inspect the hook variable. Rather than seeing a function name (from which you could jump to the nicely-formatted function definition), you see at best the lisp code all jammed into a single line, and at worst a heap of unreadable byte-code.

Use named functions. It's just better.

Check C-h v comint-process-echoes in that buffer.

If it's nil, try (setq-local comint-process-echoes t)

If that fixes it, then you can use this repl's major mode hook to do that automatically.

You mean "as opposed to using term.el" ?

Performance, mostly. (I'm still using term myself, but suspect I'll switch to eat at some point.)

However, if attempt it on a remote file (opened over tramp) it says it can’t find the binary and prompts me to point it at it. I could do that, but then the language server would start on that same machine and that’s a no go since it’s a shared login machine.

How would the local language server inspect a file which is on some other machine?

You should start by establishing how that is going to work, and add that information to your question.

Note that Emacs can interface with tools for encrypting and decrypting (and can work seamlessly with encrypted files in many cases), but Emacs itself is not performing those activities. There are many ways of encrypting things, and a decision on which approach to use is probably not going to be entirely tied to Emacs (although you'll want to be confident that the two things will work together).

If you're sold on sticking with Emacs, then learning elisp will unquestionably pay dividends, and the more you learn the more you'll be able to do (but you don't need to understand everything in order to do anything).

and how exactly can i improve my emacs experience if i learned elisp?

That's the thing -- it's up to you. The ability to "scratch any itch" is what elisp give you. That doesn't mean any given thing is easy to do (although it might be) but, to a significant extent, if you can identify a problem then implementing a solution is also a possibility.

...Coming Soon to an Emacs "Games" menu near you! 🐸

This is 100% expected behaviour. save-excursion has nothing to do with windows.

Perhaps you are confused about the phrase "...and the current buffer [is] restored". The "current buffer" is independent of the buffer in the selected window, and moreover need not be displayed at all. The current buffer is simply the buffer which is being acted on at the time.

This is 100% expected behaviour. save-excursion has nothing to do with windows.

Perhaps you are confused about the phrase "...and the current buffer [is] restored". The "current buffer" is independent of the buffer in the selected window, and moreover need not be displayed at all. The current buffer is simply the buffer which is being acted on at the time.

I feel like whenever I am browsing emacs content online there are still many topics for me to discover.

This will never not be the case.

My suggestions are:

• focus on addressing known pain points
• if something seems very popular, it might be worth trying to learn why and whether it could be beneficial to you as well
• if something else sounds super-interesting, take a look
• don't fret about not keeping abreast of everything -- it's almost certainly impractical