popper VS evil

popper: Summon, dismiss or cycle through "popup" buffers. Like drop-down terminals (guake, yakuake etc) but in Emacs and for any buffer, not just shells.

Karthink's config, good integration with the popper package

I love emacs, but agree with many of your criticisms.

Emacs can be slow. I don't use LSP, so can't comment on that, but it's definitely slow on long lines with syntax highlighting.

I don't use TRAMP for exactly one of the reasons you mentioned: it can hang Emacs. I want to avoid that at all costs, because I pretty much live in Emacs.

Handling buffers is tedious, but you can improve that through various packages, like popper[1]

Depending on what problems you run in to and your skill level, it could be tricky to debug elisp programs. However, compare that to when you run in to some bug in VSCode... how are you going to debug that? You'll probably have to submit a bug report and wait for the developers to get to it (if they ever do)... how is that better than emacs?

Also, remember that you don't have to go it alone in troubleshooting the issues you run in to with emacs. There's a whole community ready and willing to help.

Despite the downsides of emacs, I still use and love it. Every editor has downsides, and emacs is no exception. Its positives far, far outweigh the negatives for me. There's just so much more that it can do than other editors, and it's far more customizable. I very much doubt I'll ever seriously consider switching to another.

[1] - https://github.com/karthink/popper

Thanks for these tips! I'll explore tabspaces, apheleia, async-shell-command (and the Go lib) — all of those are new to me.

> Can you give a specific example of something you had trouble with?

I hoped to recreate multiple long-running terminal sessions in splits and tabs, similar to functionality I now use from:

Neovim (plugin): https://github.com/akinsho/toggleterm.nvim

VS Code (built-in): https://code.visualstudio.com/docs/terminal/basics#_managing...

I just found “popper”, which didn't exist the last time I looked. It seems like a pretty close substitute:

https://github.com/karthink/popper

I find it pretty unintuitive how magit, vterm, rg, and other commands that want to open a new window will interact with a multi-window setup. Sometimes they'll use an existing window, sometimes they'll make a new one. I prefer having things be predictable: terminals always go here, search results go there, and so on. I was looking for ways to tame this, and I found purpose, popper, shackle, and of course, directly hacking on display-buffer-alist.

I use popper for buffers I only need to see briefly.

I haven't used popper but its description sounds promising: https://github.com/karthink/popper

Maybe this can help: https://github.com/karthink/popper

Consider Popper

evil mode

Since we already have vyper-mode, why not add Evil to the stack?

2 stripe blue belt here! I used to use Vim for everything other than Java development and have now adopted Emacs in the same way. I am using it for Clojure and Common Lisp development along with org mode, irc, rss, git and file management

I started with Evil mode and then moved to Xah fly keys before sticking to the emacs bindings. Having the caps lock key bound to CTRL helped me a lot. I don't know if it makes that much of a difference for Emacs but using the DVORAK layout has helped my fingers

There are other bindings you can try like Meow or God mode but I don't know what the adoption rate is like for them. Emacs gives you the flexibility to set it up as you please. As others have mentioned, there may be other keyboard options that might be more helpful as well

https://github.com/emacs-evil/evil

If you already know Vim, you should probably not use Emacs without Evil:

https://github.com/emacs-evil/evil

It gives you comprehensive Vim bindings so what you need to learn to be comfortable in Emacs is very little. As a bonus, it also keeps your RSI risk unchanged.

Emacs is a text ecosystem. And it's trivial to add these shortcuts. Evil[0] basically rewires everything to be Vim.

[0]: https://github.com/emacs-evil/evil

I would *highly* recommend using vim keybindings if you're just getting into it (Doom or just evil). I switched from vim to emacs and tried to rough it with the default keybindings thinking that otherwise I wasn't /really/ using emacs, but I was wrong! I've been using org-mode/emacs for ~2 years now and I've slowly been migrating everything into it as I find useful tools/modes/etc (and now thanks to u/ilemming I have ~12 more to experiment with 😂)

Despite using Emacs as my main editor, I was extremely familiar with Vim since I also used it frequently, and was able to use it quite well, especially because I also used [evil](https://github.com/emacs-evil/evil) in Emacs since Emacs's native keybindings are uncomfortable to use. I never used Vim as my primary editor though because it was cumbersome to configure. As many people say, Vimscript just feels wrong, so I gave up on trying to customize Vim.

uhm... this maybe? https://github.com/emacs-evil/evil

doom is a set of configuration files (to put it lightly 😅) for emacs, a text editor with really really powerful configuration abilities -- your "config files" are actually code in a full-fledged programming language, so people have done things like built package managers in it, or written full emulators for other text editors

Does it look like this? https://github.com/emacs-evil/evil/issues/1778