On Aug 11, 10:46 am, Gary Johnson <[email protected]> wrote: > On 2011-08-11, Ben Fritz wrote: > > > On Aug 10, 5:23 pm, Linda W wrote: > > > If I put a space after $( and before th final ), then...it changes > > > the semantics of the statment > > > I think you just guaranteed I won't learn and start using bash > > scripting on a regular basis. > > Yeah, imagine trying to use a scripting language like that. Oh, > wait... > > :w!foo > :w !foo >
Touché. On the other hand this is actually consistent with the way Vim does things in general, the first is "force a write" which is consistent with "force quit", "force edit", etc. and the second is consistent with other external-command commands. It's consistent enough I never even thought about the fact that whitespace matters in this way. The other good example would be :!start vs. :! start in Windows. This one has much less reason behind it. I'm curious now, is there some decent reason the whitespace in bash script matter for semantics in the example given? -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
