zsh-workers
 help / color / mirror / code / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: bash-2.04 programmable completion
Date: 29 Nov 1999 18:53:55 +0100	[thread overview]
Message-ID: <87r9h918wc.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: Sven Wischnowsky's message of "Fri, 26 Nov 1999 12:38:28 +0100 (MET)"

Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:

> Just found this:
> 
> > From: chet@nike.ins.cwru.edu (Chet Ramey)
> > Subject: Bash-2.04 Programmable Completion message 4
> > Date: 05 Nov 1999 00:00:00 GMT
> > Message-ID: <991105173103.AA78566.SM@nike.ins.cwru.edu>
> [...]
> Two builtins `complete' and `compgen' with almost the same options,
> functions starting with underscore, -[PS] options, COMPREPLY, arrays
> holding names of stopped jobs and functions, etc.
> 
> `compgen' is lightly different from what was our `compgen', it
> obviously just outputs the possible matches. But then -- the name.

I think it would be BAD if bash had a similar system to zsh. It would
create confusion and increase work if one would want to use the same
completion scripts for both shells. So we should really try to have at
least a common base. I don't know if the two systems could be totally
compatible, since probably bash doesn't implement some needed features
like assiocative arrays. If this is impossible, the bash system should
at least not look similar.

Could probably some competent person contact the bash maintainers on
this topic?

	Falk


  reply	other threads:[~1999-11-29 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-26 11:38 Sven Wischnowsky
1999-11-29 17:53 ` Falk Hueffner [this message]
1999-11-30  9:03 Sven Wischnowsky
1999-11-30 12:41 ` Adam Spiers
1999-11-30 14:50   ` Clint Adams

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=87r9h918wc.fsf@student.uni-tuebingen.de \
    --to=falk.hueffner@student.uni-tuebingen.de \
    --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).