zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: Using the same completion function for various commands
Date: Tue, 07 Dec 2010 15:51:54 +0100	[thread overview]
Message-ID: <19832.1291733514@thecus> (raw)
In-Reply-To: <20101207115222.34859d66@pwslap01u.europe.root.pri>

Peter Stephenson wrote:
> It looks like you can't in general distinguish between two ways of using
> the service:

I don't think $service was ever intended to be usable as a command name.
The change also now assumes that the command is in your path which often
it isn't. It's also common to use /usr/gnu/bin/du and expect it to use
the GNU completions. Someone writing obscure wrappers can sooner be
expected to know what they're doing that someone specifying commands
with a full path.

> In the first case you have the simple alternative of defining
> 
> #compdef gdu
> _du "$@"
>
> which fixes the service for you.

And in the second case you have the simple alternative of using zstyle.
I've got tens of these and am not too keen on creating functions. And
why break backward compatibility?

Oliver


       reply	other threads:[~2010-12-07 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201012061512.21791.mrichter@theory.phy.tu-dresden.de>
     [not found] ` <AANLkTimY=rEETn1uOdkDJ33kGE=YUDAvevsBvvvMU7YL@mail.gmail.com>
     [not found]   ` <AANLkTim1Ac1-VOkRQ1NXn_qL6-EV06bagVkK7y_UThwB@mail.gmail.com>
     [not found]     ` <AANLkTin+NCoBRzx90fo+s0z7urCCoTA6T3cXTYdt_VD2@mail.gmail.com>
     [not found]       ` <20101206151124.389fd287@pwslap01u.europe.root.pri>
     [not found]         ` <AANLkTin8Kn88NXsK4V4Toos0-ZB2hj4RvhX5QxLarq1N@mail.gmail.com>
     [not found]           ` <15197.1291664361@thecus>
     [not found]             ` <20101207115222.34859d66@pwslap01u.europe.root.pri>
2010-12-07 14:51               ` Oliver Kiddle [this message]
2010-12-07 15:08                 ` Peter Stephenson

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=19832.1291733514@thecus \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-workers@zsh.org \
    /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).