zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: Latest CVS: configure --pre=/to does not work
Date: Mon, 22 Nov 1999 19:56:50 +0000	[thread overview]
Message-ID: <991122195650.ZM23432@candle.brasslantern.com> (raw)
In-Reply-To: <199911220934.KAA04967@beta.informatik.hu-berlin.de>

(Responding to 8716, which I pulled from my archive account as I mentioned.)

On Nov 22, 11:27am, Sven Wischnowsky wrote:
} Subject: Re: Latest CVS: configure --pre=/to does not work
}
} This patch also fixes this for me:
} 
} Tanaka Akira wrote:
} 
} > Z:akr@is27e1u11% Src/zsh -f
} > is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
} > is27e1u11% cvs <TAB>
} > CVS/           Src/           commit        init          rtag
} > Completion/    StartupFiles/  diff          log           status
} > Config/        Util/          edit          login         tag
} > Doc/           add           editors       logout        unedit
} > Etc/           admin         export        rdiff         update
} > Functions/     annotate      history       release       watch
} > Misc/          checkout      import        remove        watchers
} > 
} > Wow. filenames shouldn't listed.
} > 
} > And after second <TAB>:
} > 
} > is27e1u11% cvs --allow-root=CVS/
} > 
} > Of cause, the option `--allow-root' shouldn't completed.
} 
} That was caused by the wrong test, too.

I now get the following equally strange behavior:

zagzig<3> cvs <TAB>
add        commit     export     log        release    tag        watchers 
admin      diff       history    login      remove     unedit              
annotate   edit       import     logout     rtag       update              
checkout   editors    init       rdiff      status     watch               
zagzig<3> cvs -<TAB>
(FEEP)
zagzig<3> cvs - <TAB>
zagzig<3> cvs - --allow-root=

And --allow-root= is still the *only* option it will complete, even though
several others are passed to "_arguments -s" by _cvs.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~1999-11-22 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-22  9:34 Sven Wischnowsky
1999-11-22 13:56 ` Completion test suite Tanaka Akira
1999-11-22 19:56 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-19 15:21 Latest CVS: configure --pre=/to does not work 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=991122195650.ZM23432@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=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).