zsh-workers
 help / color / mirror / code / Atom feed
From: "E. Jay Berkenbilt" <ejb@ql.org>
To: Andrej.Borsenkow@mow.siemens.ru
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: still confused about completion and matching
Date: Fri, 20 Oct 2000 16:45:50 -0400	[thread overview]
Message-ID: <200010202045.QAA13963@soup.ql.org> (raw)
In-Reply-To: <000401c03ab6$d95b92d0$21c9ca95@mow.siemens.ru> (Andrej.Borsenkow@mow.siemens.ru)


>   >			      The single remaining command I used to have a
>   > programmable completion for in tcsh that I don't in zsh is smbclient.
>   > I plan to eventually write a completion function for smbclient and
>   > submit it.  This should be much simpler than this _path_files stuff,
>   > especially if I read Etc/completion-style-guide.
>   >
>
>   Good move I say. Well, look at the _arguments, it should be
>   enough. There are plenty of examples - most of completion functions
>   now-a-days are implemented using this great tool. The only problem
>   I forsee is, that smbclient has options after arguments (at least,
>   that is how they are listed in man pages).  _arguments normally
>   expect reverse order.
>
>   But I do not know, if smbclient really requires it, and am too lazy
>   to look in sources :-)

I don't think it's really true.... I've never had anything odd about
smbclient's argument ordering.  I was going to use cvs as a model
since it is smart enough to use cvs with some of the existing
arguments to get the module list.  The same type of idea could be used
do completion for share names once the server has been specified.

I'll use this as incentive to get my current project finished -- my
reward will be letting myself play with zsh completion functions. :-)
It will probably be at least a week before I can start it.

>   Also, if you could send comments (or even patches) for _arguments
>   documentation ...

You can count on it!  Once I get up to a certain level of competence
I'd like to do a thorough cover-to-cover read of the zsh documentation
with red pen in hand.  (I'll probably print the .yo files directly --
easier to generate patches and make comments that way.  Besides, I've
been considering whether to use yodl for some of my own documentation.
This way I could find out whether I like it or not. :-]) I have
written enough documentation to know how important it is to have a
fresh set of eyes read it.  One eventually becomes immune to errors in
one's own writing. :-) I don't know when I'll get to this but
hopefully before the next non-development release which I guess is
supposed to be 4.0?

>   Of course, completing server and share names is a bit demanding
>   ... but it is well possible in Zsh.

See above.  Thanks.

--
E. Jay Berkenbilt (ejb@ql.org)  |  http://www.ql.org/q/


  reply	other threads:[~2000-10-20 20:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19  9:11 Sven Wischnowsky
2000-10-20 16:38 ` E. Jay Berkenbilt
2000-10-20 16:57   ` Andrej Borsenkow
2000-10-20 20:45     ` E. Jay Berkenbilt [this message]
2000-10-23  7:15       ` Andrej Borsenkow
2000-10-23 13:11         ` E. Jay Berkenbilt
  -- strict thread matches above, loose matches on Subject: below --
2000-10-25  7:50 Sven Wischnowsky
2000-11-06 15:34 ` E. Jay Berkenbilt
2000-10-25  7:12 Sven Wischnowsky
2000-10-25  7:41 ` Andrej Borsenkow
2000-10-24  7:44 Sven Wischnowsky
2000-10-24 15:00 ` E. Jay Berkenbilt
2000-10-24 15:15   ` Bart Schaefer
2000-10-24 15:28     ` Andrej Borsenkow
2000-10-23 13:20 Sven Wischnowsky
2000-10-16  8:05 Sven Wischnowsky
2000-10-17 19:30 ` E. Jay Berkenbilt
2000-10-13 11:03 Sven Wischnowsky
2000-10-12 19:56 E. Jay Berkenbilt
2000-10-12 20:32 ` E. Jay Berkenbilt
2000-10-16  5:01 ` Bart Schaefer

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=200010202045.QAA13963@soup.ql.org \
    --to=ejb@ql.org \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --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).