Re: PATCH: $CONTEXT

[Peter Stephenson <pws@csr.com>]

Oliver Kiddle wrote:
> Peter wrote:
> > Here is the zle parameter CONTEXT.  There are four contexts start, cont,
> > select, vared.  Let me know if you think there should be more.
> 
> Would `primary' and `secondary' perhaps be better values for `start'
> and `cont'?  That would tie up more closely with the documentation for
> PS1 and PS2.

Maybe, but it's a bit ugly, and a bit less obvious what it's for.

> As for other values, reading from the minibuffer probably ought to be
> relevant but I suspect it isn't.  Replacing accept-line caused me
> problems from it.  Menu selection and scrolling came to mind but they
> take place from a primary or secondary prompt. If we're going to have a
> number of different minor things, a zlestate associative array like
> compstate might be better.

Yes, these are slightly different and not actually orthogonal to the
primary context.

> Would it perhaps be worth making a convention of sticking this $CONTEXT
> in a second component of the zstyle context (after :zle:) when looking
> up styles from zle widgets?

On reflection, this makes some sense... you might different word
behaviour in a vared than at the command line, for example.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************