From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@math.gatech.edu
Cc: bobg@zanshin.com
Subject: Another patch to compctl-examples CVS compctl, and a bug?
Date: Sat, 13 Jul 1996 17:34:22 -0700 [thread overview]
Message-ID: <960713173425.ZM5697@candle.brasslantern.com> (raw)
It's now possible to avoid several external processes in generating the
list of CVS-controlled files in the `cvstargets' function. The key is
this wonderful "parameter" (boy, is that misnamed) subsitution:
"${${${(f@)$({<${pref}CVS/Entries} 2>/dev/null)}#/}%%/*}"
This almost bears explaining in and of itself. The {...} are needed
around the nullcmd input redirection, so that the 2> redirection won't
be improperly parsed as part of the file name (see my previous report).
The $(...) substitution grabs the contents of the CVS/Entries file to
get a list of all files in the current directory that CVS knows about.
This is wrapped in ${(f@)...} to force each line to be interpreted as
a separate word; this works because of the outer double quotes. Next
is ${...#/} to strip a leading slash from every line of the CVS/Entries
file. Finally, this is wrapped in ${...%%/*} to strip from each line
everything following the file name itself.
If there's a better way than `for f in ... do echo ... done' to prefix
every element of the resulting array with ${pref}, I'd love to see it.
Now for the bug: If the ${pref}CVS/Entries file exists, all of this
works fine. However, if no CVS directory exists at all, the above
subsitution prints a newline to the terminal -- which messes up zle.
The newline is not going into $reply, because using <redisplay> or
<clear-screen> and then continuing a menu completion cycles through
the other choices without further zle confusion.
Where is that newline coming from?
The other interesting (and the slow) part of $reply is:
${pref}*/**/CVS(:h)
which returns names of any directories below the ${pref} directory that
in turn contain a CVS subdirectory.
Hmm, maybe all that should get added to the comments in the file. :-}
*** Misc/compctl-examples.0 Fri Jul 5 10:57:42 1996
--- Misc/compctl-examples Sat Jul 13 16:50:40 1996
***************
*** 439,447 ****
pref=
fi
[[ -n "$pref" && "$pref" != */ ]] && pref=$pref/
! reply=($(for f in $(cat ${pref}CVS/Entries 2>/dev/null | \
! sed 's/^\/\([^\/]*\).*/\1/'); do echo $pref$f; done)
! $(echo ${pref}**/CVS(:h) | sed 's/CVS//'))
}
#------------------------------------------------------------------------------
# RedHat Linux rpm utility
--- 439,448 ----
pref=
fi
[[ -n "$pref" && "$pref" != */ ]] && pref=$pref/
! reply=($(for f in \
! "${${${(f@)$({<${pref}CVS/Entries} 2>/dev/null)}#/}%%/*}" \
! do echo $pref$f; done)
! ${pref}*/**/CVS(:h))
}
#------------------------------------------------------------------------------
# RedHat Linux rpm utility
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
next reply other threads:[~1996-07-14 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-14 0:34 Bart Schaefer [this message]
1996-07-14 1:55 ` Bart Schaefer
[not found] ` <schaefer>
1996-07-14 2:00 ` Bart Schaefer
1996-07-17 21:52 ` Completion behavior change in 3.0-pre3 Bart Schaefer
1996-07-19 19:53 ` Another patch to compctl-examples CVS compctl, and a bug? Bart Schaefer
1996-07-22 7:34 ` Peter Stephenson
1996-07-22 6:53 ` Bug in case stmt with '(' Bart Schaefer
1996-07-15 1:02 ` Another patch to compctl-examples CVS compctl, and a bug? Zoltan Hidvegi
1996-07-15 2:32 ` Bart Schaefer
1996-07-15 4:30 ` Zoltan Hidvegi
1996-07-15 7:03 ` Bart Schaefer
1996-07-15 17:02 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1996-07-16 6:00 Completion behavior change in 3.0-pre3 Bart Schaefer
1996-07-17 9:52 ` Christoph von Stuckrad
1996-07-17 15:29 ` Bart Schaefer
[not found] <199607191600.SAA08613@bolyai.cs.elte.hu>
[not found] ` <9607211853.ZM979@morgan.com>
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=960713173425.ZM5697@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=bobg@zanshin.com \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).