From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Corrected style test in prediction
Date: Wed, 23 Feb 2000 15:42:30 +0000 [thread overview]
Message-ID: <1000223154230.ZM11815@candle.brasslantern.com> (raw)
In-Reply-To: <200002231046.LAA16578@beta.informatik.hu-berlin.de>
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
next prev parent reply other threads:[~2000-02-23 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-23 10:46 Sven Wischnowsky
2000-02-23 15:42 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-23 15:53 Sven Wischnowsky
2000-02-23 15:48 Sven Wischnowsky
2000-02-23 9:44 Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000223154230.ZM11815@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).