I've made no statement about emacs or evil mode. I was just correcting the user I was responding to about vim having interoperability with the rest of unix
> They live in their own space, you don't (often) pipe stuff in or out of it.
Well that's not true at least for vim.
: read !FOO
will run the FOO command and read the results back into the current buffer. I usually search my codebase by reading the results of a grep into a temporary buffer and 'gf'ing to the appropriate file
Yes. I opened alacritty for the first time, wondered why my greens were showing up as yellow and googled it. This was the first result.
I doubt my comment is going to torpedo anything. But I didn't put down alacritty for "personality" reasons. There are a lot of excellent terminal emulators out there. This github issue wasn't an isolated incident, and if the devs are regularly this hostile there's bound to be lots of issues like this that won't be fixed. Especially since my OS is only nominally supported.
Yes, it can be frustrating when your users don't know as much about your product as you do and ask for help in a vague way. It's unintuitive that a color named green would correspond to the color on the left that I don't think most people would think to check.
It's totally fine to have a policy of not supporting OSX, as long as you communicate it with professionalism or at least civility.
The other dev chiming in at the end with "I've heard only good things about Alacritty's default colorscheme so far" was also frustrating. Saying "well nobody else complained" is an awful reason to dismiss an issue.