From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _urls, _netscape, a seg fault and new completion thoughts
Date: 14 Oct 1999 23:28:28 +0900 [thread overview]
Message-ID: <rsqk8oq3tkj.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Thu, 14 Oct 1999 13:41:10 +0200 (MET DST)"
In article <199910141141.NAA13535@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> diff -u -r oldcompletion/Core/_main_complete Completion/Core/_main_complete
> --- oldcompletion/Core/_main_complete Wed Oct 13 16:18:19 1999
> +++ Completion/Core/_main_complete Thu Oct 14 13:38:04 1999
> @@ -55,6 +57,24 @@
> "$post"
> done
> comppostfuncs=()
> +
> +_lastdescr=( "\`${(@)^_lastdescr:#}'" )
> +if [[ compstate[nmatches] -eq 0 &&
> + -n "$compconfig[warning_format]" && $#_lastdescr -ne 0 ]]; then
> + local str
> +
> + compstate[list]=list
> + compstate[force_list]=yes
> + compstate[insert]=''
> +
> + case $#_lastdescr in
> + 1) str="$_lastdescr[1]";;
> + 2) str="$_lastdescr[1] or $_lastdescr[2]";;
> + *) str="${(j:, :)_lastdescr[1,-2]}, or $_lastdescr[-1]";;
> + esac
> +
> + compadd -UX "${compconfig[warning_format]//\\%d/$str}" -n ''
> +fi
>
> [[ "$compconfig[last_prompt]" = always ]] && compstate[last_prompt]=yes
>
I couldn't apply this hunk.
Z:akr@rascal% patch --dry-run -p0 < ../patchsrc/zsh-workers/8249
patching file Src/Zle/compctl.c
patching file Src/Zle/compctl.mdd
patching file Doc/Zsh/compctl.yo
patching file Doc/Zsh/compsys.yo
patching file Completion/Builtins/_nothing
patching file Completion/Core/_description
patching file Completion/Core/_files
patching file Completion/Core/_main_complete
Hunk #1 succeeded at 24 with fuzz 2.
Hunk #2 FAILED at 57.
1 out of 2 hunks FAILED -- saving rejects to file Completion/Core/_main_complete.rej
patching file Completion/Core/_message
patching file Completion/Core/_multi_parts
patching file Completion/Core/_path_files
patching file Completion/Core/_sep_parts
zsh: exit 1 patch --dry-run -p0 < ../patchsrc/zsh-workers/8249
I searched `comppostfuncs' in my zsh-workers archive, but a patch for
_main_complete which contains `comppostfuncs' was not found.
Z:akr@rascal% grep comppostfuncs ../patchsrc/zsh-workers/8???
../patchsrc/zsh-workers/8227:widgets. So I added the `comppostfuncs' array which is normally
../patchsrc/zsh-workers/8227:About this `comppostfuncs' business: some time ago we discussed ways
../patchsrc/zsh-workers/8227:what-we-have, the `comppostfuncs' array may look more useful.
../patchsrc/zsh-workers/8227:+functions whose names are given in the tt(comppostfuncs) array and
../patchsrc/zsh-workers/8227:+ comppostfuncs=( "$post[@]" )
../patchsrc/zsh-workers/8227:+ [[ "$twid" = "$wid" ]] && comppostfuncs=( "$post[@]" )
../patchsrc/zsh-workers/8249: comppostfuncs=()
Z:akr@rascal%
Maybe, a patch for _main_complete was forgotten in 8227.
--
Tanaka Akira
next prev parent reply other threads:[~1999-10-14 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-14 11:41 Sven Wischnowsky
1999-10-14 14:28 ` Tanaka Akira [this message]
1999-10-14 14:39 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=rsqk8oq3tkj.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).