zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Standard setopts for completion system, again
Date: Wed, 18 Oct 2000 04:31:31 +0000	[thread overview]
Message-ID: <1001018043131.ZM3958@candle.brasslantern.com> (raw)
In-Reply-To: <1001006145848.ZM25084@candle.brasslantern.com>

On Fri, 6 Oct 2000 I wrote:
} Unfortunately, we heavily recommend autoloading all completion functions
} with "autoload -U", which means an alias won't be expanded!

It occurred to me somewhat later that, even with "autoload -U", an alias
*would* be expanded during an "eval".  So we could put this:

alias _comp_setopt='setopt nullglob rcexpandparam extendedglob unset \
     no{markdirs,globsubst,shwordsplit,shglob,ksharrays,cshnullglob}'

into compinit, and then in the completion functions like _main_complete:

eval _comp_setopt localoptions

Another choice (still in compinit) would be simply to stuff the desired
options into an array:

_comp_setopts=(nullglob rcexpandparam extendedglob unset
     no{markdirs,globsubst,shwordsplit,shglob,ksharrays,cshnullglob})

and then reference them:

setopt localoptions $_comp_setopts

I guess I slightly prefer the latter, since we're already cluttering the
parameter space with completion stuff and I'd rather stay out of the alias
space, but either one would be OK.

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

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  parent reply	other threads:[~2000-10-18  4:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-06 12:53 Sven Wischnowsky
2000-10-06 14:58 ` Bart Schaefer
2000-10-06 16:11   ` Option completion after "nono" Bart Schaefer
2000-10-18  4:31   ` Bart Schaefer [this message]
2000-10-18  7:13 PATCH: Re: Standard setopts for completion system, again Sven Wischnowsky
2000-10-18  7:28 ` Andrej Borsenkow
2000-10-19  8:57 Sven Wischnowsky

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=1001018043131.ZM3958@candle.brasslantern.com \
    --to=schaefer@candle.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).