zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] complete two or more options for zsh
Date: Fri, 25 Sep 2015 10:03:03 -0700	[thread overview]
Message-ID: <150925100303.ZM3552@torch.brasslantern.com> (raw)
In-Reply-To: <91D49604-A261-46A4-95BC-624420629B84@kba.biglobe.ne.jp>

On Sep 26,  1:04am, Jun T. wrote:
}
} Anyway, yes, it's better to do all the completion by _arguments alone.
} How about the patch below?
} (or is it better to create _zsh to do the completion for zsh only?).

If the zsh case is never going to use any of the common code for other
shells, then it would probably be better to create an _zsh.  I'm
trying to think of ways that might fail to be backward-compatible with
existing compdef configs, but not coming up with anything.

} > Hm.  Is this a bug in _arguments rather than in the way that _sh
} > called _arguments?  That is, should descr ever be a single ":"?
} 
} If there is ever an intended effect of specifying '*:' as a helpspec,
} then it would better to fix _arguments to do the intended job.
} 
} So anyway '*:' seems to have no effect on how the options are ordered.
} What is the intended effect of '*:' as a help spec?

The person who could definitively answer that hasn't read this list in
at least a decade.  Maybe someone else remembers, but I don't.


  reply	other threads:[~2015-09-25 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-19 19:27 Jun T.
2015-09-23  5:39 ` Bart Schaefer
2015-09-25 16:04   ` Jun T.
2015-09-25 17:03     ` Bart Schaefer [this message]
2015-09-30 16:03       ` Jun T.
2015-09-30 16:19         ` Bart Schaefer
2015-10-01 10:41           ` Jun T.

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=150925100303.ZM3552@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).