From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: partial word completion
Date: Mon, 3 Apr 2000 14:17:57 +0200 (MET DST) [thread overview]
Message-ID: <200004031217.OAA01262@beta.informatik.hu-berlin.de> (raw)
Some recent changes made a small bug show up, where, for example,
completion on an empty word in a directory with `foo.bar.baz' and
`boo.far.faz' inserted `.'.
The problem was that too many cline structs got the CLF_NEW flag
removed (CLF_NEW indicates newly build parts without anything
corresponding on the line).
Bye
Sven
P.S.: Are the log messages and the version numbers (_path_files went
from 1.2 to 1.4) ok, or am I doing something wrong?
P.P.S.: Yeah, right, I haven't tried to understand everything about
CVS' version numbering facilities yet.
P.P.P.S.: Have I just made a fool out of myself?
Index: Src/Zle/compmatch.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/compmatch.c,v
retrieving revision 1.2
diff -u -r1.2 compmatch.c
--- Src/Zle/compmatch.c 2000/04/01 20:49:48 1.2
+++ Src/Zle/compmatch.c 2000/04/03 11:58:52
@@ -351,7 +351,6 @@
p = bld_parts(s, sl, osl, &lp);
- p->flags &= ~CLF_NEW;
if (m && (m->flags & CMF_LEFT)) {
lp->flags |= CLF_SUF;
lp->suffix = lp->prefix;
@@ -384,7 +383,8 @@
lp->line = l; lp->llen = wl;
lp->word = w; lp->wlen = wl;
lp->orig = o; lp->olen = ol;
- lp->flags &= ~CLF_NEW;
+ if (o || ol)
+ lp->flags &= ~CLF_NEW;
/* Finally, put the new parts on the list. */
if (matchlastpart)
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-04-03 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 12:17 Sven Wischnowsky [this message]
2000-04-17 7:55 Sven Wischnowsky
2000-04-18 1:20 Felix Rosencrantz
2000-04-18 7:06 Sven Wischnowsky
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=200004031217.OAA01262@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).