41–50 of 57 posts
Nvim+plugins gives me pretty much all I need, and there's usually always some vi variant on any linux env I've had to use.
This is why I will pretty much always using a vi-like editor. Currently using vim/nvim/Doom Emacs depending on which machine I'm using, but it is _extremely_ helpful to be able to have a common set of keybinds which I can use to at least comfortably edit config files on *nix.
Vim simply gives the best editing experience, and together with the old Vim plugins and the newer Neovim plugins it gives me everything I'd want and more.
it is always there.
it loads instantly.
it can handle filesizes that make other editors croak.
PHPStorm cause I'm retro cool. I tried VSCode, but it takes more time to set up for PHP and doesn't do some things quite as well. For example, the interface for traversing classes or finding references is a little less refined than in PHPStorm. Perhaps more tricks are available and I could get used to different things, but I have no complaints.
PHP with PhpStorm is like a flakey Java.
It’s amazing what that IDE did to that language. It’s the only way to write a lot of PHP.
VSCode, with Vim emulation. I almost never want for Vim stuff that doesn't exist in the Code plugin. I generally am happy with Code's autocomplete and plugin ecosystem. Really feels like the best of both worlds to me.
For config file editing, VS code if available. Otherwise (SSH, visudo, other CLI-only situation) I use whatever is available (usually vim or nano).
I tend to use Notepad++ on Windows for some things, since it's got good support for keyboard macros which are sometimes faster to use than sed or awk.