You can keymap ctrl-c, ctrl-v, ctrl-a to copy/paste,select all. I map these this way when using gvim in windows to copy to the windows clipboard which is really nice and makes it so gvim plays very naturally with other windows applications. If using windows, I recommend using gvim - it is less painful than using terminal based vim or nvim for a newer user.
For what itâs worth, you can tell Emacs to use Ctrl-X / Ctrl-C / Ctrl-V the same way as most text editors, but only in a limited capacity, and in certain modes. It also clobbers a lot of useful key combinations.
Emacs not seeing the X11 clipboard when running in a terminal is one reason why I still use Micro as well, at least locally. Emacs-GTK does the right thing though.
@BFelsher âIf vim ceased to exist, I would quit programming.â
@rwmsu "Me too. I can safely say âI vim therefore I amâ "
Surely, these are very extreme comments for an IDE
I have used different IDE options but avoided VS Code because Itâs Microsoft.
I have used a variety of options on a Windows PC, which include multiple screens, an IDE, Notepad and cmd.exeâs findstr.
Happy to change if a better option comes along.
vim is not an IDE which is the main reason I prefer it. Iâve yet to find any IDE (or other GUI based tool) that makes me more productive than just vim and a command line. In the time it takes to navigate the multiple layers of menus and menu items that GUI developers seem to think are âcoolâ I can get real work done. I settled on vim a long time ago when most of my work involved logging in remotely to a front end system for a large Cray or SGI HPC system from a Linux/Unix workstation through an SSH client. vim worked just fine in that environment. Something I could never get any GUI based tool to do reliably. Also, I gave up on Windows 30 plus years ago and havenât looked back.
Tried lazyvim but it got to be too much like an IDE, and like @rwmsu I prefer simplicity or I get too distracted and before I know it Iâve wasted hours screwing around instead of coding.
On windows for almost 20 years I used to use a program called EditPadPro. It was just so easy to configure external tools, and itâs still around. Thereâs a free version, but I paid the $50 for the full version.
There are a lot of options for using Emacs on MacOS. You can run it as a standalone application, or in an X11 window (with XQuartz), or in a terminal window (which is what I usually do). Then within each of those there are further configuration options on how keystrokes are mapped and how the various clipboards, kill rings, and pasteboards interact. With XQuartz for example (which you can install with Homebrew), look under XQuartz->Settings->Pasteboard for some of these options. It does help to have a 3-button mouse for some of these, which is the way Xwindows has always been. There is no shortage of configuration options within Terminal, XQuartz, Emacs, and within MacOS itself.
I prefer simplicity: (tmux) + vim + fortls.
The caption of that xkcd strip reminded me of an episode of Futurama where they explain that the shipâs engine is particular in that it doesnât move the ship⌠It moves the universe instead, 
.
I have been using emacs, both in GUI and in terminal, for the last few decades. Occasionally, for fast fixes, microemacs. Recently I tried to pair emacs with fortls a few times, also using hints from this forum, but to no success 
My current setup works well (with fortls too), but I often entertain the idea of using emacs again, since it is highly configurable and I could use it in the terminal. However, Iâd want to make sure tools like fortls work well. Have you used other tools with emacs, like fortitude?
No, I have not.