zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [RFC] Teach getopts to handle -o and +o separately
Date: Thu, 11 Oct 2018 20:26:04 +0000	[thread overview]
Message-ID: <1539289564.4186713.1539035184.7FD78E44@webmail.messagingengine.com> (raw)
In-Reply-To: <9A1ABCB6-0FF1-4E8E-83BE-3B8D84954525@dana.is>

dana wrote on Wed, 10 Oct 2018 20:33 -0500:
> Of course, this eliminates - and + as valid 'letters' in the optstring. But it
> seems unlikely that anyone actually needs +-, -+, or ++ (-- is already
> effectively unusable for obvious reasons). Also, POSIX says:

FWIW, ezmlm-make(1) has a -+ flag.  Not saying it's a deal breaker; just a datapoint.

      reply	other threads:[~2018-10-11 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  1:33 dana
2018-10-11 20:26 ` Daniel Shahaf [this message]

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=1539289564.4186713.1539035184.7FD78E44@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --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).