zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Andrew Markebo <flognat@flognat.myip.org>
Cc: zsh-users@sunsite.dk
Subject: Re: Completion or.. expansion..
Date: Wed, 25 Jul 2001 08:27:17 +0000	[thread overview]
Message-ID: <1010725082717.ZM17354@candle.brasslantern.com> (raw)
In-Reply-To: <m3ofq9bhgh.fsf@localhost.localdomain>

On Jul 25,  9:23am, Andrew Markebo wrote:
} Subject: Re: Completion or.. expansion..
}
} Hmm ok, then.. time to reformulate the question.. I want to configure
} what TAB does :-) I assume that is Completion then. 

Hmm, ok, then, time to reformulate the answer.

bindkey '\t' expand-or-complete	# Does expansion first, or else completion
bindkey '\t' complete-word	# Does completion only

The default binding if you don't re-bindkey it is expand-or-complete.

If you put the word "_expand" anywhere in your completer zstyle, though,
the `compinit' function (a call to which is added to your ~/.zshrc by
`compinstall') will automatically rebind '\t' from expand-or-complete
to complete-word.

So the upshot probably is that you don't need to worry about it at all.
Just leave it alone, run compinstall, and the right things will happen.

} | > setopt glob bareglobqual nullglob rcexpandparam extendedglob unset
} | >   unsetopt markdirs globsubst shwordsplit shglob ksharrays cshnullglob
} | >   unsetopt allexport
} | > 
} | > Should I use these, or do something with completion, compinstall?
} | 
} | Where did you find those three (un)setopt commands, and why do you think
} | you need them?
} 
} Just an example from my side, sort of "is it these I should poke
} on?" (from the zsh users guide) or are they replaced by 
}         "zstyle ':completion:*' completer _list ..."
} or do they work together? If I have got stuff right, the zstyle
} replaces them?

None of those setopts has anything whatsoever to do with completion, with
the possible exception of `markdirs'.  So no, the zstyles don't replace
*those* options, but there *are* some *other* options that zstyles either
replace or augment.

That's why I ask, "Where did you find *those* commands, and why ...?"

} So basically.. remove all my options for completion, run compinstall
} and live happily for the rest of the time :-)?

More likely, it's leave all your options exactly as they are, run
compinstall, and live happily.

-- 
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   


  reply	other threads:[~2001-07-25  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 21:16 Andrew Markebo
2001-07-25  1:00 ` Bart Schaefer
2001-07-25  7:23   ` Andrew Markebo
2001-07-25  8:27     ` Bart Schaefer [this message]
2001-07-25  8:34       ` Sven Wischnowsky
2001-07-25  9:32       ` Peter Stephenson

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=1010725082717.ZM17354@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=flognat@flognat.myip.org \
    --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).