Use hard-coded limit to keep it simple. An alternative is to dynamically
calculate the width of the visible area and use it as the limit, but it
can cause unwanted truncation of the query on screen resize/split.

Fix typo in comment

[fzf-tmux] Make fzf target correct session in group

Fixes #643
Doesn't break #648

This reverts commit 4d444777.

[fzf-tmux] Fix grouped tmux session confusion

[zsh-completion] Split default zsh binding at the correct place

Avoids confusing grouped sessions.
Fixes #643

The command substitution and following word splitting to determine the default
zle widget for ^I formerly only works if the IFS parameter contains a space. Now
it specifically splits at spaces, regardless of IFS.

Related #642

Fix #520
Fix junegunn/fzf.vim#42

fzf#wrap([name string,] [opts dict,] [fullscreen boolean])

- Make structs smaller
- Introduce Result struct and use it to represent matched items instead of
  reusing Item struct for that purpose
- Avoid unnecessary memory allocation
- Avoid growing slice from the initial capacity
- Code cleanup

By only using leaf functions

Sort performance increases as the size of each sublist decreases (n in
nlog(n) decreases). Merger is then responsible for merging the sorted
lists in order, and since in most cases we are only interesed in the
matches in the first page on the screen so the overhead in the process
is negligible.

https://golang.org/doc/go1.5

Approx. 50% less memory footprint and 40% improvement in query time

In the best case (all ascii), this reduces the memory footprint by 60%
and the response time by 15% to 20%. In the worst case (every line has
non-ascii characters), 3 to 4% overhead is observed.

Fix #636. Patch suggested by @edi9999.

Fix #183