zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completion in vared
Date: Fri, 30 Apr 1999 11:40:57 -0700	[thread overview]
Message-ID: <990430114057.ZM18502@candle.brasslantern.com> (raw)
In-Reply-To: <199904300707.JAA21821@beta.informatik.hu-berlin.de>

On Apr 30,  9:07am, Sven Wischnowsky wrote:
} Subject: Re: completion in vared
}
} 
} Bart Schaefer wrote:
} > By the way, if we're reasonably confident that we've now identified all
} > the compctl-isms that it's useful to put into compadd/gen/etc., I think
} > we should seriously look at rewriting the option parsing for those new
} > commands to abandon the compctl syntax.
} 
} I /think/ you are referring to an old suggestion to just give a
} builtin that gets the matches to be added directly (that would be
} compadd) and let the user generate these matches/words through shell
} code.

No, I'm mostly thinking of the compctl options that have poor mnemonics,
and particularly of -J and -V (which are begging for a bracketed-looking
syntax).

There is some advantage to having the options of the new commands be the
same as those of compctl, but I'm not sure if it's enough to outweigh the
opportunity to clean it up a bit.

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


  reply	other threads:[~1999-04-30 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-30  7:07 Sven Wischnowsky
1999-04-30 18:40 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-05-03  8:14 Sven Wischnowsky
1999-04-29  9:05 Sven Wischnowsky
1999-04-29 16:42 ` Bart Schaefer
1999-04-28 15:00 Peter Stephenson
1999-04-28 17:59 ` 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=990430114057.ZM18502@candle.brasslantern.com \
    --to=schaefer@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).