zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Oliver Kiddle" <opk@u.genie.co.uk>, <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: _zmodload
Date: Mon, 21 Aug 2000 10:04:13 +0400	[thread overview]
Message-ID: <000001c00b35$a19fcab0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200008181443.PAA95540@cm01.ess>

> 
> Well here is the _arguments version and I've also tried to make use of
> the $modules parameter where possible. Is my strategy of retricting the
> arguments to _tags and then completing everything in the while _tags
> loop okay? It seems to work and was the easiest way I could find to
> handle _zmodload seeing as it has all the flags first.
> 

This lists modules twice - once with extension and once without:

bor@itsrm2% zmodload zsh/cap
Completing module file
cap               cap.so*           clone             clone.so*       
compctl           compctl.so*       complete          complete.so*    
complist          complist.so*      computil          computil.so*    
deltochar         deltochar.so*     example           example.so*     
files             files.so*         mapfile           mapfile.so*     
mathfunc          mathfunc.so*      parameter         parameter.so*   
rlimits           rlimits.so*       sched             sched.so*       
stat              stat.so*          zftp              zftp.so*        
zle               zle.so*           zleparameter      zleparameter.so*
zprof             zprof.so*         zpty              zpty.so*        
zutil             zutil.so*                                         

-andrej


  reply	other threads:[~2000-08-21  6:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-16  9:23 PATCH: $modules (was: Re: Seg fault with zmodload -u) Sven Wischnowsky
2000-08-16  9:45 ` Peter Stephenson
2000-08-18 14:43 ` PATCH: _zmodload Oliver Kiddle
2000-08-21  6:04   ` Andrej Borsenkow [this message]
2000-08-21  8:00 Sven Wischnowsky
2000-08-21  8:34 ` 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='000001c00b35$a19fcab0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=opk@u.genie.co.uk \
    --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).