From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: PATCH: (was Re: _configure does not work)
Date: Tue, 9 Mar 1999 13:54:14 +0100 (MET) [thread overview]
Message-ID: <199903091254.NAA14116@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 9 Mar 1999 14:36:10 +0300
Andrej Borsenkow wrote:
> After applying last patches (5696-5699) I get some strange results:
>
> 1. bor@itsrm2:/tools/src/zsh-3.1.5-pws-11%> ./configure --pre<TAB>
> bor@itsrm2:/tools/src/zsh-3.1.5-pws-11%> ./configure --pre44
> fix=
Maybe I'm too tired today to fiddle with the code... this is the
output of an `echo' I had inserted for debugging.
> 2. l ~/.z/C<TAB>
> Beep
> ~/.zsh.d/Completion exists and was correctly completed before a couple of
> last patches :-)
Hm, this works for me.
> 3. (I think, it changed recently)
>
> ./configure --e-d<TAB>
> ./configure --enable-dynamic <^Xu> (bound to undo)
> ^cursor here (one blank after line)
> ./configure --enable-dynamic <^Xu>
> ^cursor still here
> ./configure --e-d
>
> Well, IMHO ``--enable-dynamic '' (including blank) was inserted in _one_
> step and should be removed by _one_ command as well. And it was the case at
> least with 3-1.5-pws-10.
This is the auto-removable suffix. I faintly remember a discussion
about undoing and inserted suffixes where some people wanted to have
different `undo's for the suffix and the word. (If you don't see a auto-
removable suffix, just type a space, tab, or newline after the
`--enable-dynamic ').
So, what do (and others) think, should the first `undo' undo
everything, should this be done only if the suffix was a automatically
inserted space, should there be an option,...?
Bye
Sven
--- oc/User/_long_options Tue Mar 9 11:31:54 1999
+++ Completion/User/_long_options Tue Mar 9 13:10:14 1999
@@ -89,7 +89,7 @@
opts=("--${(@)^${(@)${(@)${(@M)${(@ps:\n:j:\n:)${(@)${(@M)${(@f)$("$words[1]" --help)}:#[ ]#-*}//,/
}}:#*--*}#*--}%%[, ]*}:#(*-[A-Z]*|)}")
-echo $#opts
+
# The interpretation of the options is completely table driven. We
# use the positional parameters we were given and a few standard
# ones. Then we loop through this table.
@@ -298,7 +298,7 @@
compadd -M 'r:|-=* r:|=*' -Q "$suffix[@]" -s "$str" - \
"${(@P)name}" && ret=0
elif [[ -z "$str" ]]; then
- compadd -M 'r:|-=* r:|=*' -Q -s "$str" - \
+ compadd -M 'r:|-=* r:|=*' -Q - \
"${(@P)name}" && ret=0
fi
done
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-03-09 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 12:54 Sven Wischnowsky [this message]
1999-03-09 14:04 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
1999-03-09 14:25 Sven Wischnowsky
1999-03-09 16:47 ` Andrej Borsenkow
1999-03-09 13:58 Sven Wischnowsky
1999-03-09 13:09 Sven Wischnowsky
1999-03-09 13:37 ` Andrej Borsenkow
1999-03-09 10:32 Sven Wischnowsky
1999-03-09 10:47 ` Andrej Borsenkow
1999-03-09 11:36 ` Andrej Borsenkow
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=199903091254.NAA14116@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).