From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: PATCH: Omissions (Re: pws-23)
Date: Sun, 20 Jun 1999 18:16:26 +0000 [thread overview]
Message-ID: <990620181627.ZM14728@candle.brasslantern.com> (raw)
In-Reply-To: <9906201528.AA13442@ibmth.df.unipi.it>
The first hunk of Sven's 6414 is missing. This may be intentional, because
it fixes one bug by introducing another less-likely one, but the ChangeLog
says it should be there.
Index: Src/Zle/zle_tricky.c
===================================================================
@@ -735,7 +735,7 @@
*b != '=' && *b != Equals &&
*b != '~' && *b != Tilde)
break;
- if (*b == '#' || *b == Pound || *b == '+')
+ if (*b == '#' || *b == Pound || *b == '+' || *b == ' ')
b++;
e = b;
The documentation in compsys.yo from Sven's 6686 is also missing.
Index: Doc/Zsh/compsys.yo
===================================================================
@@ -474,6 +474,12 @@
`tt(*)' will be inserted. If tt(match_original) has any other non-empty
string as its value, this completer will first try to generate matches
without, then with a `tt(*)' inserted at the cursor position.
+
+The generated matches will be offered in a menucompletion unless the
+tt(match_insert) configuration key is set to a string starting with
+`tt(unambig)'. In this case menucompletion will only be started if no
+unambiguous string could be generated that is at least as long as the
+original string.
)
item(tt(_expand))(
This completer function does not really do completion, but instead
@@ -707,10 +713,13 @@
`tt(-S)', `tt(-q)', `tt(-r)', and `tt(-R)' options from the
tt(compadd) builtin.
-Finally, the tt(_path_files) function supports one configuration key:
-tt(path_expand). If this is set to any non-empty string, the partially
+Finally, the tt(_path_files) function supports two configuration keys.
+If tt(path_expand) is set to any non-empty string, the partially
typed path from the line will be expanded as far as possible even if
-trailing pathname components can not be completed.
+trailing pathname components can not be completed. And if
+tt(path_cursor) is set to a non-empty string, the cursor will be left
+after the first ambiguous pathname component even when menucompletion
+is used.
)
item(tt(_parameters))(
This should be used to complete parameter names if you need some of the
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-06-20 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-20 15:28 pws-23 Peter Stephenson
1999-06-20 17:15 ` pws-23 Bart Schaefer
1999-06-21 7:15 ` pws-23 Peter Stephenson
1999-06-20 17:28 ` PATCH: Spelling error (Re: pws-23) Bart Schaefer
1999-06-20 18:16 ` Bart Schaefer [this message]
1999-06-21 7:51 PATCH: Omissions " 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=990620181627.ZM14728@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).