Actually Print EditorConfig Warning Messages

[samontea]

Editorconfig overrides existing language code style settings in favor of project defined style guides in the form of .editorconfig file. This package does require an external dependency for the emacs package. We need to indicate to the user that they need to install this dep.

[samontea]

None of our existing packages require an external dependency. I felt like this merited more discussion about how to deal with this. cc: @rye @cg505

[rye]

I agree. EditorConfig is a good example of something that should exist in our configuration, because it's a great feature from our previous configurations that worked very well in contributing to projects that use an esoteric code style e.g. soft tabs or hard tabs.

The external dependency for EditorConfig is a program (EditorConfig C Core) that can be run on the host machine. I agree that we should figure out how to deal with cases like these; I'd imagine we don't want to install external dependencies for our users, but it might make sense to point them to a Wiki entry—through a minibuffer warning or something like that—for the different edge cases where the host environment doesn't have everything available.

[cg505]

#10 #18
I straight up thought we already had this working

[rye]

#18, too.

As with most PR's, this is low-impact and adds functionality so it doesn't matter too much if it's broken.

I guess this is broken. We tried to add it before but it seems like it's not working.

[samontea]

okay so I guess the only remaining issue is indicating to the user that they should install the external dep. I updated the issue to reflect this.

[rye]

Yeah the lwarn doesn't actually print anything out because its level is set to debug.

[rye]

We can open another issue for hypotheticals.