See :help &lt;D-. Use &lt;D-t&gt; to map to ⌘-T; however, ⌘-T is already mapped to "New Tab" within MacVim's menu. You'll have to remove that to be able to use it in a Vim map.

Some keys are OS-bound and you just can't access them, but ⌘-T can be made available and is actually the example they use in the help file (see :help Actions.plist and scroll up a few lines to 4.). You'll need to unset the "New Tab" binding with

:macmenu File.New\ Tab key=&lt;nop&gt;


and then map ⌘-T with nnoremap &lt;D-t&gt; whatever.

Command key in MacVim
I live in a small town in rural Nebraska.  When I do a tracert from my home to the small college where I work it hops to Dallas, then Denver, and then Chicago before coming back here.  That seems very odd to me, not to mention inefficient.  But then, I have a completely different ISP at home, so I'm not even sure if it's all that unusual.

So, my questions are, is this even really a problem, as long as the packets do get where they're supposed to go?  And since this is all upstream of anything I control, can I even do anything about it (aside from complaining to the ISPs involved) if it is?

The tracert looks like this:

  1     1 ms     1 ms     1 ms  10.1.1.2 
  2     2 ms     1 ms     1 ms  192.168.254.254 
  3     9 ms     9 ms     9 ms  h1.80.29.71.dynamic.ip.windstream.net [71.29.80.1] 
  4    21 ms     9 ms    10 ms  h222.28.213.151.static.ip.windstream.net [151.213.28.222] 
  5    29 ms    30 ms    29 ms  h140.254.213.151.static.ip.windstream.net [151.213.254.140] 
  6    34 ms    30 ms    30 ms  h130.254.213.151.static.ip.windstream.net [151.213.254.130] 
  7    30 ms    30 ms    29 ms  xe-8-3-0.edge3.Dallas1.Level3.net [4.71.198.25] 
  8    42 ms    34 ms    34 ms  ae-72-70.ebr2.Dallas1.Level3.net [4.69.145.115] 
  9    52 ms    52 ms    52 ms  ae-2.ebr1.Denver1.Level3.net [4.69.132.105] 
 10    52 ms    53 ms    53 ms  ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38] 
 11    69 ms    68 ms    68 ms  ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62] 
 12    74 ms    69 ms    69 ms  ae-1-51.edge2.Chicago2.Level3.net [4.69.138.131] 
 13    69 ms    68 ms    68 ms  ROADRUNNER.edge2.Chicago2.Level3.net [4.59.28.110] 
 14    69 ms    68 ms    71 ms  ae-1-0.cr0.chi10.tbone.rr.com [66.109.6.152] 
 15    69 ms    69 ms    69 ms  ae-15.chcgileq-rtr1.kc.rr.com [66.109.6.101] 
 16    87 ms    86 ms    86 ms  xe-1-2-0.lnclne00-mx42.neb.rr.com [76.85.220.134] 
 17    87 ms    85 ms    86 ms  xe-0-0-0.lnclne00-mx41.neb.rr.com [76.85.220.145] 
 18    86 ms    85 ms    85 ms  gig2-1.lnclne00-dar1.neb.rr.com [76.85.220.110] 
 19    87 ms    86 ms    87 ms  rrcs-76-79-19-35.west.biz.rr.com [76.79.19.35] 

It's just weird, because I'll give good odds that the link between Denver and Chicago follows I-80, which means we're up to three passes right by the campus before it finally arrives (one on the way out of town, one going from denver to chicago, and the one back in from chicago).
