zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _rlogin splits up into three functions (still one file)
Date: Wed, 4 Oct 2000 16:03:12 +0000	[thread overview]
Message-ID: <1001004160312.ZM22931@candle.brasslantern.com> (raw)
In-Reply-To: <200010040954.LAA09415@beta.informatik.hu-berlin.de>

On Oct 4, 11:54am, Sven Wischnowsky wrote:
} 
} Bart Schaefer wrote:
} 
} > 	#compdef krlogin krsh krcp
} > 	compdef ${words[1]:t:s/k/_/} ${words[1]:t}
} > 	_rlogin "$@"

I just realized that the above won't work properly unless one of the k*
forms is the first thing completed.  If _rlogin has already been auto-
loaded, call to _rlogin there is wrong.

It could be written

	[[ $functions[_rlogin] == "builtin autoload -X" ]] &&
	    _rlogin "$@" || $_comps[${words[1]:t}] "$@"

or some such, but that's pretty silly.

So ...

} This gave me the idea of adding one more (probably optional, i.e. not
} used everywhere) level of indirection when mapping a command name to a 
} completion function. So that _rlogin could offer the `services'
} `_rlogin', `_rsh' and whatnot.

This actually sounds like a reasonable idea.  There'd have to be a way
for the #compdef tag line to register all the "services" provided by the
file in which the tag appears.  I still don't see any obvious way to
fully automate this part --

} > +[[ $_comps[rsh] == _rlogin ]] && compdef _rsh rsh
} > +[[ $_comps[remsh] == _rlogin ]] && compdef _rsh remsh
} > +[[ $_comps[rcp] == _rlogin ]] && compdef _rcp rcp

-- but I haven't been thinking about it for very long.

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

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-10-04 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-04  9:54 Sven Wischnowsky
2000-10-04 16:03 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-19  5:10 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=1001004160312.ZM22931@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).