zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Default compctls
Date: Sat, 6 Jul 1996 12:07:27 -0700	[thread overview]
Message-ID: <960706120731.ZM17740@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: Default compctls" (Jul  6,  8:10pm)

On Jul 6,  8:10pm, Zoltan Hidvegi wrote:
} Subject: Re: Default compctls
}
} I think compctls belong to the user-level code.  Adding new default
} compctls just increase zsh size and it is quite useless as these are
} usually overriden by the user.

I can't imagine that this is all that significant in terms of size.
Anyway, surely you agree that `builtin' should be corrected from
`compctl -c' to `compctl -B'?

I'd actually be happy to go the other way and REMOVE all the default
compctls except for:

compctl -C -c
compctl -D -f
compctl -T

However, it seems silly to me to have defaults (and incorrect ones at
that) for some builtins, yet not supply the obvious defaults for others.

} Zsh is quite unusable without good startup files anyway.

I wouldn't say that.  I've used it without startup files quite a lot, for
reasons too baroque to bother explaining here.

} > compctl -c -		# BUG!  `-' has special meaning to `compctl'!
} 
} I think -- should mean the end of completion flags as it already means that
} with extended completions.

There are several inconsistencies in zsh as to whether `--' means end
of flags, or whether a solitary `-' means end of flags.  I.e. zsh `echo`
seems to be unique among other shells and /bin/echo in that zsh strips
a solitary leading `-' out of the args to be echoed (no others do).
(Others that I tried don't strip `--' either, though.)

} > Is there any workaround for the bug noted above?
} 
} No, but
} 
} compctl -c exec -
} 
} works.

If I do that and then utter `compctl -L` I get:

compctl -c - -

which does work in the way `compctl -L` implies that it should.  Good.

} Note that Misc/compctl-examples contains better
} compctl's for command, exec, moglob, -.  Look at the section near line 52.

Yes, but I was trying to restrict myself to "simple" compctls because
they should be relatively painless to build in -- a few bytes and one
or two function calls added to compctlsetup(), is all.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



  reply	other threads:[~1996-07-06 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-06 17:50 Bart Schaefer
1996-07-06 18:10 ` Zoltan Hidvegi
1996-07-06 19:07   ` Bart Schaefer [this message]
1996-07-06 18:38 ` Zefram
1996-07-06 20:01   ` 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=960706120731.ZM17740@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).