WallyMetropolis

Being able to do emacs stuff in my terminal and terminal stuff in my emacs while sharing the same kill ring and other similar kinds of state.

The killer feature is emacs lisp. Once you've gotten a handle on the general, day to day use of emacs and the packages in your quiver the next step is to learn the language that powers the system. This will open up an incredible amount of power and customizability. It will change what you think emacs is, fundamentally.

Writing your own functions, modes, and packages is the thing that makes emacs emacs. Right now, you configure your system. But once you learn emacs lisp you will be able to customize it. This is a huge difference.

Oh man, if you had this connected to your primary monitors and used it just for the minibar and completion results and such, somehow, that would be incredible.

I want to echo what /u/rwilcox said. Emacs isn't really about maxing out speed. It's certainly possible with a lot of effort, but that's not the fundamental principle of emacs or it's reason for existing.

Emacs is about customization. Not configurability, but customization. And, because you can do so many different tasks with emacs, it's about staying in emacs as much as possible. Using a single tool for almost everything and avoiding context switching. I use emacs for coding and debugging sure, but also for git, merges and diffing, for a REST client, for my shell, for taking notes, for managing a personal knowledge system, for managing contacts, for keeping my agenda and todo list, for my calendar, for creating pdfs with latex, for creating and displaying presentations. I don't read and compose email in emacs just yet, but I'll probably get around to setting that up, too. So my only tools are emacs and a browser.

And, when I'm using emacs, I get to use it more or less exactly how I want, depending on how much effort I was willing to put into setting up how I want it to behave. For example, I added some functions to look up words under the cursor on Dictionary.com and search for synonyms on Thesaurus.com, and to do so interactively so I can select a synonym from the list and either look up its definition or search for synonyms of that word and then replace the current word with the synonym. I later found some other package for doing a similar kind of thing, but it wasn't that hard to just write it for myself. Or, I added some functions to maintain a list of commonly used but useless words like "really" and highlight them in a text so they can be replaced. Or a mode to follow a certain editing workflow that works well for me. With all these tools together, writing and editing documents is quite a pleasant experience. And I can tweak any piece of it, or tweak how each interacts with the others.

I haven't worried too much about hyper-optimizing efficiency. I just don't find that particularly useful. But there are still certain kinds of common tasks I can do very very fast. Like refactoring code by pulling every instantiation of a class I've changed into a single buffer and adding or changing the call to the constructor with multiple cursors and then saving them all, all in one shot. That's always pretty spiffy.

That I cannot answer. Never used that flag. Maybe try grepping the magit package.

That's why I said 'also.'

I would also suggest fetch. Pull is fetch and merge. So if you don't want to merge, you can just fetch.

I think the Mermaid Gantt charts look incredible and they are extremely feature-rich. I'm a huge fan of that project.

As a side note, it's too bad that "ts" has become the default convention for treesitter modes because it always makes me think of TypeScript first.

If anyone would like any other useless opinions on things I don't contribute at all to, please, feel free to ask.