From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Another patch to compctl-examples CVS compctl, and a bug?
Date: Sun, 14 Jul 1996 19:32:39 -0700 [thread overview]
Message-ID: <960714193241.ZM1933@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: Another patch to compctl-examples CVS compctl, and a bug?" (Jul 15, 3:02am)
On Jul 15, 3:02am, Zoltan Hidvegi wrote:
} Subject: Re: Another patch to compctl-examples CVS compctl, and a bug?
}
} > "${${${(f@)$({<${pref}CVS/Entries} 2>/dev/null)}#/}%%/*}"
}
} There are two problems with that. First I've modified the lexer so that
} !, [[, { and } are reserved words now. This means that these must be
} delimited. So {echo} no longer works, { echo } should be used instead.
} Similarily [[-z $foo]] does not work, [[ -z $foo ]] should be used.
Hmm. I don't think anything else I've done depends on that, but given
that we're already at 3.0-preN for N >1, it seems a rather bad time to
make the change.
} The other problem is that this depends on READNULLCMD being cat.
It depends on READNULLCMD being something that knows when its output
is not a terminal, at least; "less" and "more" both work just as well
as "cat".
} $(<...) always works since it is always recognized as a special command
} substitution. That's why the 2> redirection does not work in that case
Still seems like a bug to me.
} > 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.
}
} It's simply
}
} "${pref}${^${${(f@)$({<${pref}CVS/Entries} 2>/dev/null)}#/}%%/*}"
I thought something like that should work, but I never tried the carat
in that particular spot.
} > works fine. However, if no CVS directory exists at all, the above
} > subsitution prints a newline to the terminal -- which messes up zle.
}
} Are you sure that there is not empty element in the reply?
Why should that make a difference? It still shouldn't output a newline.
} The above `parameter expansion' always produces at least one element.
Here's the behavior I see in a directory that has no CVS subdirectory:
If I replace my `for ... echo' loop with your ${^...} solution above,
then *every* time I hit TAB I get a newline on the terminal, and I
never see any completions. (Your solution works normally in a dir
that *does* have a CVS subdir.)
If I use my `for ... echo' loop, I get a newline the first time I hit
TAB. The second time I hit TAB I get the leading hyphen from the -k
array of option letters, followed by a newline, followed by `A' (the
first option letter). From that point on I get no stray newlines, and
the options cycle normally (though zle is confused if I don't do a
<redisplay> at some point.
If I use your solution with an explicit "cat", I don't get any newlines,
but I also don't get any completions -- not even the -k ones.
If I switch back to an explicit "cat" and use my original `for' loop,
everything works exactly as I would expect -- no stray newlines at all,
and all the expected -k completions appear.
So it has something to do with READNULLCMD, and there's something else
broken about your solution. (Maybe that's where the empty element in
the array is involved?)
--
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 prev parent reply other threads:[~1996-07-15 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-14 0:34 Bart Schaefer
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 [this message]
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=960714193241.ZM1933@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=hzoli@cs.elte.hu \
--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).