Vim Tip: Fix plugin loading error “Not an editor command: ^M”

This post is a preservation of the now inactive: https://nlknguyen.com/2016/06/03/vim-tip-fix-plugin-loading-error-not-an-editor-command-m/

One of the most annoying errors you probably already encountered  with Vim terminal (not GVim) on Windows when you use Vim plugins that were obtained through Git (via plugin manager like Vundle, Pathogen, etc.) is this kind of error message:

E492: Not an editor command: ^M
line    9:
E182: Invalid command name
line   10:
E492: Not an editor command: ^M
line   12:
E182: Invalid command name
line   13:
E492: Not an editor command: ^M
line   15:
E182: Invalid command name
line   16:
E492: Not an editor command: ^M
line   18:
E182: Invalid command name

This error is reported and asked so many times on StackOverflow and GitHub, and the answers provided are mostly about removing the special character or setting file format to “unix”. However, that wouldn’t solve the problem.

It took me a very long time (I gave up many times) to finally find out the solution through this GitHub issue on Vundle. It wasn’t something many people would expect. Turned out Git’s default setting to deal with line endings is not sufficient.

All you need to do is to config your Git correctly before cloning Vim plugins:

$ git config --global core.autocrlf input

That’s it. Now you can install Vim plugins like normal.

For more information about the above Git setting, see here.

Future of Dark Room

Much has changed in the years since Dark Room was originally written, and there are many options available at this time. Thus, the question to be asked is, does continued development of DR make sense? I spent a significant amount of time rewriting the application from scratch to run as an adobe air application. I did this because I was no longer using windows at the time, so dedicating some much time on a .net application did not make a lot of sense, thus a cross platform solution seemed more desirable. Unfortunately, Adobe dropped linux support shortly before the first beta release of the new program. So, I essentially stopped development on it.

I still want to have a cross platform application. I began trying to find new viable options, and I was just about to start a write up in python when I discovered FocusWriter. It is a cross platform distraction free environment, and it uses QT. It’s written in C++, which I don’t really like, but I could deal with it. I would almost say it is enough to use FocusWriter, but it is missing some key functionality from Dark Room I couldn’t live without. Therefore, at this point I am seriously considering forking FocusWriter in order to add in the additional Dark Room functionality.

Thoughts?

Screaming Fast, Like its 2004!

Due to the death of my good computers, I have found myself relegated to my PowerMac G5. Surprisingly this machine is stilling going strong. Fortunately, I had replaced the video card, and maxed the ram a few years ago.

But, the hard drive in this thing was so freaking loud that something had to be done. I debating getting a newer drive on the hope that it would be quieter, but decided to bite the bullet and just get a solid state drive. Now that I have run it for a couple of days, I have to say that this machine is running as fast as it possibly can. Which means it is actually quite useable. IO operations are pretty good, the age is really only noticeable on CPU intensive activities.

Authorize.net Partial Auth Doc

I have a heck of a time digging this up when I want it so I am posting the link for everyone

http://developer.authorize.net/guides/SIM/Transaction_Data_Requirements/partial_auth.htm

http://www.authorize.net/support/merchant/Transaction_Response/Response_Reason_Codes_and_Response_Reason_Text.htm#243

http://community.developer.authorize.net/t5/Integration-and-Testing/Triggering-Specific-Transaction-Responses-Using-Test-Account/td-p/4361