Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Corrected style test in prediction
- X-seq: zsh-workers 9843
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: Corrected style test in prediction
- Date: Wed, 23 Feb 2000 15:42:30 +0000
- In-reply-to: <200002231046.LAA16578@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200002231046.LAA16578@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Feb 23, 11:46am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Corrected style test in prediction
}
} Bart Schaefer wrote:
}
} > Sven, please confirm ... I'm never sure about the number of trailing colons.
} >
} > Index: Functions/Zle/predict-on
} > ===================================================================
} > - elif zstyle -t ":completion:predict::::" list always
} > + elif zstyle -t ":completion:::predict::" list always
}
} The number of colons is still correct, but the original context name
} was correct, too. The `predict' was stored in the `function' field of
} the context name, indicating that completion was called from predict.
But in insert-and-predict we have:
local crs curcontext="${curcontext}"
[[ -z "$curcontext" ]] && curcontext=:::
curcontext="${curcontext#*:}predict:"
which makes the context be :completion:::predict::, with `predict' in
the `command' field. Surely the two should be the same? If not, why
not?
} However, the other call to zstyle had a missing colon, the one before
} the (not-given) tag.
Well, that part at least is less confusing now.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author