From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: PATCH: 3.1.5-pws-6: compctl manual inevitable follow-up
Date: Wed, 03 Feb 1999 10:09:52 +0100 [thread overview]
Message-ID: <9902030909.AA43991@ibmth.df.unipi.it> (raw)
Bad karma in my compctl manual patch: too many @enditem's. For some
reason this only showed up when running texinfo. Then, of course, I
had to change the text just before again.
--- Doc/Zsh/compctl.yo.tidy2 Tue Feb 2 17:20:05 1999
+++ Doc/Zsh/compctl.yo Wed Feb 3 10:08:42 1999
@@ -784,13 +784,13 @@
indent(
tt(compctl -M 'r:|[.,_-]=* r:|=*' 'l:|=* r:|=*')
)
-So, if the string on the command line is tt(foo.bar), tt(compctl) first
-tries matching tt(foo)var(anything)tt(.bar)var(anything), and if that
-fails will look for var(anything)tt(foo.bar)var(anything);
-the two descriptions in the second string say that the
-empty string at the beginning and end of the string on the line
-matches any set of characters at the beginning or end of the word.
-enditem()
+Here, if the string on the command line is tt(foo.bar), tt(compctl)
+first tries matching tt(foo)var(anything)tt(.bar)var(anything), as
+with the previous example. If that fails, the two descriptions in the
+second string after the tt(-M) say that the blanks at the beginning
+and end of the string on the command line can match any set of
+characters at the beginning or end of the trial completion, so it will
+look for var(anything)tt(foo.bar)var(anything).
texinode(Example)()(Matching Control)(Programmable Completion)
sect(Example)
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
reply other threads:[~1999-02-03 9:09 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=9902030909.AA43991@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--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).