zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Corrected style test in prediction
Date: Wed, 23 Feb 2000 16:48:33 +0100 (MET)	[thread overview]
Message-ID: <200002231548.QAA14791@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 23 Feb 2000 15:42:30 +0000


Bart Schaefer wrote:

> } 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?

Ouch. Thanks for the hint.

Bye
 Sven

diff -ru ../z.old/Functions/Zle/predict-on Functions/Zle/predict-on
--- ../z.old/Functions/Zle/predict-on	Wed Feb 23 14:44:05 2000
+++ Functions/Zle/predict-on	Wed Feb 23 16:47:41 2000
@@ -56,7 +56,7 @@
 	  local crs curcontext="${curcontext}"
 
           [[ -z "$curcontext" ]] && curcontext=:::
-          curcontext="${curcontext#*:}predict:"
+          curcontext="predict:${curcontext#*:}"
 
 	  comppostfuncs=( predict-limit-list )
 	  zle complete-word

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-02-23 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-23 15:48 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-23 15:53 Sven Wischnowsky
2000-02-23 10:46 Sven Wischnowsky
2000-02-23 15:42 ` Bart Schaefer
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=200002231548.QAA14791@beta.informatik.hu-berlin.de \
    --to=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).