ace-window VS evil-collection

Thanks that is helpful. I do have a question though. Is there any plugin similar to ace-window? I frequently have a situation where I have two frames (basically two windows) that are connected to the same Emacs process, and I am jumping between buffers in both frames.

Looks good. But https://github.com/abo-abo/ace-window was a game-changer for me :-)

take a look at https://github.com/abo-abo/ace-window

I recently started using workspaces in my workflow, and although I know many packages are available in Emacs such as the ones mentioned in the comments, but what worked for me so far is just make a second frame and use ace-window with the variable aw-scope set to 'frame. And from there I just move one frame to the appropriate workspace in my desktop environment and that's it. It's worth keeping in mind that the buffers are still shared so might not be the perfect workspace experience, but I don't think that matters in Emacs.

Try the ace-window package. I think you're referring to C-x o which is bound to other-window.

Also highly recommend ace-window.

I'd like to use ffap (to open files/dirs) in windows I select with ace-window (https://github.com/abo-abo/ace-window). Similar to what aw-switch-buffer-in-window and aw-switch-buffer-other-window do, but with find-file-at-point instead of buffer selection. Crucially, the point means the where I am when the function is called.

If someone has a big monitor I recommend changing C-x 1 delete-other-windowsto revert to have 2 windows open, (like in this config) and using ace-window to navigate to your many windows.

Ace-Window is meant to replace `other-window' by assigning each window a short, unique label

It looks like that package has an issue tracker here, if you wanted to raise one: https://github.com/emacs-evil/evil-collection/issues

Honestly, I've yet to find a plugin that I use that isn't covered by https://github.com/emacs-evil/evil-collection. I love emacs, but I can't stand the chords.

Evil and Evil Collection is the nuclear option.

I still have phases where I experiment with modal editing, but I haven't messed with Evil-mode in a long time. I prefer Meow, in part because it doesn't invest everything on a single command layout. And the sample Dvorak layout meshes really well with Emacs bindings for special modes (like Dired and Ibuffer). So you don't have to install and configure something like Evil-collection just to use the same bindings everywhere.

The problem I have with evil in Emacs is that it is another layer on top of vinalla Emacs. Not many packages are designed with evil key bindings in mind. You need packages like https://github.com/emacs-evil/evil-collection and and https://github.com/emacs-evil/evil-magit and https://github.com/emacs-evil/evil-ediff to make Emacs feel more "evil". Distros like Doom and Spacemacs integrate these packages for you, but then you're even farther away from the default Emacs experience. I also find online help worse for evil bindings. To figure stuff out you often have to resort to looking at vim or neovim documentation. "Vanilla" Emacs is famously "self documenting" but last I checked evil couldn't provide useful help, within Emacs, in the same way.

Evil does interfere with bindings in some modes, but https://github.com/emacs-evil/evil-collection fixes a lot of these issues, both for built-in modes and a lot of popular third-party ones.

Oh, and stick this in your use-package for general: ;; We want SPC as a leader key, probably. So do this. It just affects what ;; keybinds are overridden by the `override' keymap functionality that ;; `general' provides. ;; ;; https://github.com/emacs-evil/evil-collection#making-spc-work-similarly-to-spacemacs ;; ;; NOTE: `evil-collection' binds over SPC in many packages. To use SPC as a ;; leader key with `general', first set these override states: (setq general-override-states '(insert emacs hybrid normal visual motion operator replace))

You might want to look into the evil-collection package.

Evil mode is incredible, but it has real disadvantages in the Emacs context. It is another layer above Emacs, which makes Emacs different from its default self. E.g. most packages don't come with evil-mode key bindings. The popular Emacs packages are handled by https://github.com/emacs-evil/evil-collection but, there is always going to be a layer of translation between how upstream describes its key bindings and how Evil binds them.