Re: PATCH: key bindings, fixes, docs, tests for vi stuff

[Mikael Magnusson <mikachu@xxxxxxxxx>]

On Fri, Nov 21, 2014 at 2:15 AM, Ray Andrews <rayandrews@xxxxxxxxxxx> wrote:
> pts/11 HP-y5--5-Debian1 root /aMisc/Ray1 $ l Etc/FA1:
>
> text.c:865: unknown word code in gettext2()
> 82: text.c:865: unknown word code in gettext2()
> 178: text.c:865: unknown word code in gettext2()
> 178: text.c:865: unknown word code in gettext2()
> 1: text.c:865: unknown word code in gettext2()
> 117: text.c:865: unknown word code in gettext2()
> 38: text.c:865: unknown word code in gettext2()
> 40: text.c:865: unknown word code in gettext2()
> 1: text.c:865: unknown word code in gettext2()
> 15: text.c:865: unknown word code in gettext2()
> 115: text.c:865: unknown word code in gettext2()
> 118: text.c:865: unknown word code in gettext2()
> 18: text.c:865: unknown word code in gettext2()
> 121: text.c:865: unknown word code in gettext2()
> 17: text.c:865: unknown word code in gettext2()
> 864: text.c:865: unknown word code in gettext2()
> Q.yo
> zsh-5.0.7-86-ga3cc409
>
> That popped up as I was trying to complete '/Etc/FAQ.yo'

If you use dev versions of zsh, you will sometimes need to manually
purge your .zwc files as they're not compatible across some code
changes. We bump the version on release and avoid loading them in that
case, but when running code from git there is no way to detect this
currently. (I suppose we could stick the patchlevel in there, but that
would invalidate the wordcode needlessly often).

-- 
Mikael Magnusson