SUBRATIONAL

I love Vim, but I also have Ctrl+X, Ctrl+C, Ctrl+V permanently burned into my brain. Can we consolidate these two worlds? Yes! Mostly.

mswin.vim is distributed with Vim and offers some hints, but it brings a bit of extra baggage, and still doesn’t behave as I’d expect. Instead, I am doing the following:

vnor <C-X> "+x
vnor <C-C> "+y
inor <C-V> <C-O>:set paste<CR><C-R>+<C-O>:set nopaste<CR>
vnor <C-V> :<C-U>set paste<CR>gvc<C-R>+<C-O>:set nopaste<CR><ESC>

• You can cut and copy in visual mode.
• You can paste in insert mode or visual mode (replacing your selection).
• Pasting does not result in poor formatting.
• Ctrl+V still does visual block selection.

For me, at least, this scheme offers the best tradeoffs with the least surprise.

Cut and copy are just using the + clipboard register, and paste is just doing <C-R>+ (see :h i_ctrl-r) in between paste/nopaste to preserve the text without having Vim reformat it. Ugly, but it works.

If you’re trying to play HTML5 video with the <video/> tag, ensure the correct Content-Type header is being sent for your source media.

Some browsers, such as Chrome, seem willing to play a video regardless of its Content-Type (perhaps through sniffing or file extensions), but others, such as IE, require a valid and supported value.

I ran into this while trying to play videos hosted on S3 with IE10:

<video controls autoplay>
  <source src="http://s3-us-west-1.amazonaws.com/foo/bar.mp4" type="video/mp4" />
</video>

Even with the type attribute set to video/mp4, IE refused to play the video, saying only “Invalid Source” or “Error: Unsupported video type or invalid file path”. Some searching yielded this blog post detailing common problems.

The error coming from the video element in IE was MEDIA_ERR_SRC_NOT_SUPPORTED. In my case, the source wasn’t supported because the MIME type being sent was not supported:

$ curl -I http://s3-us-west-1.amazonaws.com/foo/bar.mp4
HTTP/1.1 200 OK
Date: Fri, 14 Jun 2013 03:24:53 GMT
Last-Modified: Fri, 14 Jun 2013 03:24:40 GMT
Content-Type: application/octet-stream
Content-Length: 9227881
Server: AmazonS3
...

Apparently after uploading the video, S3 automatically set its Content-Type to application/octet-stream, which IE does not support.

This is normally not a problem when serving videos from a web server such as Apache, since the server is usually configured to send the Content-Type header based on the file extension, but many cloud storage services like S3 require you to specify your own metadata.

We were uploading videos using the AWS Ruby SDK, so the fix was to simply specify :content-type when uploading the file via S3Object#write:

obj.write(:content_type => 'video/mp4', ...)

If you need to support a wider range of MIME types, consider using the mime-types gem and MIME::Types.type_for.