From: Sweth Chandramouli <svc@sweth.net>
To: zsh-users@sunsite.dk
Subject: Re: compctl -g not working
Date: Wed, 3 Oct 2001 02:15:24 -0400 [thread overview]
Message-ID: <20011003021524.A15356@astaroth.sweth.net> (raw)
In-Reply-To: <1011003060441.ZM25764@candle.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 5545 bytes --]
On Wed, Oct 03, 2001 at 06:04:41AM +0000, Bart Schaefer wrote:
> On Oct 3, 12:12am, Sweth Chandramouli wrote:
> }
> } On Wed, Oct 03, 2001 at 04:04:49AM +0000, Bart Schaefer wrote:
> } > Glob completion shouldn't have anything to do with it.
> } ??? Why not, given that that's what I'm having problems
> } with?
>
> Because `compctl -g' forces a glob to happen. Glob completion (as in the
> glob_complete option) only determines how completion proceeds when there
> is a partial match.
Ah. I meant glob completion as in "compctl using
globs", rather than "completion using glob_complete", especially since
glob_complete doesn't actually use globbing (according to the man page).
> } > So you're going to have to give us some more clues.
> } I don't suppose you could give me any clues as to where
> } I should look for more clues? :)
>
> Well, for one thing, you ought to try running a newer version than
> 3.1.9.
That wouldn't help me figure out what was broken,
however. I'm stubborn enough to want to waste my time trying to
figure out what changed, rather than just changing other things until
it works. Upgrading to 4.x is on my todo list, however.
> But what I meant was, for example, tell us what your setopts actually
> are rather than ask us what they might not be,
OK; I was trying to not waste space with the full list if
others could give me tips as to where to focus my search. Here's the
full list:
(astaroth)~: allopt
allexport off
alwayslastprompt on
alwaystoend off
appendhistory on
autocd off
autolist on
automenu on
autonamedirs off
autoparamkeys off
autoparamslash on
autopushd on
autoremoveslash on
autoresume off
badpattern on
banghist on
bareglobqual on
bashautolist off
beep off
bgnice on
braceccl on
bsdecho off
cdablevars off
chasedots off
chaselinks off
checkjobs on
clobber off
completealiases on
completeinword on
correct on
correctall off
cshjunkiehistory on
cshjunkieloops off
cshjunkiequotes off
cshnullcmd off
cshnullglob off
dvorak off
equals on
errexit off
exec on
extendedglob on
extendedhistory on
flowcontrol off
functionargzero off
glob on
globalexport on
globalrcs on
globassign off
globcomplete off
globdots on
globsubst on
hashcmds on
hashdirs on
hashlistall off
histallowclobber off
histbeep off
histexpiredupsfirst on
histfindnodups off
histignorealldups on
histignoredups on
histignorespace off
histnofunctions off
histnostore on
histreduceblanks on
histsavenodups on
histverify off
hup on
ignorebraces off
ignoreeof off
incappendhistory on
interactive on
interactivecomments on
ksharrays off
kshautoload off
kshglob on
kshoptionprint on
listambiguous on
listbeep on
listpacked off
listrowsfirst off
listtypes on
localoptions on
localtraps off
login off
longlistjobs on
magicequalsubst off
mailwarning off
markdirs on
menucomplete off
monitor off
multios on
nomatch on
notify on
nullglob off
numericglobsort off
octalzeroes off
overstrike off
pathdirs off
posixbuiltins on
printeightbit on
printexitvalue off
privileged off
promptbang on
promptcr on
promptpercent on
promptsubst on
pushdignoredups off
pushdminus off
pushdsilent off
pushdtohome on
rcexpandparam on
rcquotes off
rcs on
recexact on
restricted off
rmstarsilent off
rmstarwait off
sharehistory on
shfileexpansion off
shglob on
shinstdin on
shnullcmd off
shoptionletters off
shortloops on
shwordsplit off
singlecommand off
singlelinezle off
sunkeyboardhack off
unset on
verbose off
xtrace off
zle off
> tell us in which version
> of zsh these same compctls last worked if they ever did,
3.1.9; I've been using it for at least a year, and at some
point the completion worked. I made some changes many months ago,
but hadn't used any of the commands whose compctls used -g in at least
the last six months.
> what happens
> if you run `zsh -f' and then add the suspicious compctls one at a time,
They work fine under zsh -f; sorry for not mentioning that
in my original post.
-- Sweth.
--
Sweth Chandramouli ; <svc@sweth.net>
President, Idiopathic Systems Consulting
[-- Attachment #2: Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2001-10-03 6:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 2:53 Sweth Chandramouli
2001-10-03 3:16 ` Philippe Troin
2001-10-03 3:18 ` Sweth Chandramouli
2001-10-03 4:04 ` Bart Schaefer
2001-10-03 4:12 ` Sweth Chandramouli
2001-10-03 6:04 ` Bart Schaefer
2001-10-03 6:15 ` Sweth Chandramouli [this message]
2001-10-03 16:24 ` Bart Schaefer
2001-10-03 18:23 ` Sweth Chandramouli
2001-10-04 4:23 ` Bart Schaefer
2001-10-04 4:43 ` Sweth Chandramouli
2001-10-05 16:13 ` Bart Schaefer
2001-10-05 16:23 ` Zefram
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=20011003021524.A15356@astaroth.sweth.net \
--to=svc@sweth.net \
--cc=zsh-users@sunsite.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).