From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: unambiguous string insertion
Date: Thu, 17 Feb 2000 13:36:08 +0100 (MET) [thread overview]
Message-ID: <200002171236.NAA22416@beta.informatik.hu-berlin.de> (raw)
While playing with _multi_parts some more I noticed that it inserted
unambiguous strings such as `.' or `..'. This patch avoids silly
things like these again.
Bye
Sven
diff -ru ../z.old/Src/Zle/compresult.c Src/Zle/compresult.c
--- ../z.old/Src/Zle/compresult.c Thu Feb 17 12:57:50 2000
+++ Src/Zle/compresult.c Thu Feb 17 13:30:04 2000
@@ -64,7 +64,8 @@
q = p;
}
if (!e && q && !q->orig && !q->olen && (q->flags & CLF_MISS) &&
- !(q->flags & CLF_MATCHED) && (q->word ? q->wlen : q->llen) < 3) {
+ (!(q->flags & CLF_MATCHED) || (!q->prefix && !q->suffix)) &&
+ (q->word ? q->wlen : q->llen) < 3) {
q->word = q->line = NULL;
q->wlen = q->llen = 0;
}
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
reply other threads:[~2000-02-17 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200002171236.NAA22416@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).