zsh-workers
 help / color / mirror / code / Atom feed
From: Josh Howard <jrh@kashmir.vicor-nb.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Lack of any functionality in new completion
Date: 23 Mar 1999 10:27:17 -0800	[thread overview]
Message-ID: <yfg1zigqcxm.fsf@kashmir.vicor-nb.com> (raw)
In-Reply-To: Sven Wischnowsky's message of "Tue, 23 Mar 1999 14:46:59 +0100 (MET)"

Well, I with I can't seem to find any relation to setopting those and
it actually doing anything. If I go in to ~/.zsh/ (where I put most of 
the scripts) and do something silly like an 'autoload _*', I get
slightly different behavior. If I do an 'ls -l _pa^D', I get the same
line repeated, such as:

jrh@kashmir:~/.zsh> ls _par^D
jrh@kashmir:~/.zsh> ls _par
Same thing as with ^I instead of ^D

And the file _parameter is in that directory.

I tried this with as vanilla of a zsh as I could try, ie, none of my
previous startup files to no avail. 

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

> Josh Howard wrote:
> 
> > Hitting ^I/tab seems to do absolutely nothing, however. Is there 
> > something I'm simply missing?
> > Sorry if this is just vast ineptitude on my part, but I guess
> > things just aren't going my way.
> 
> Have you got it working already? There is also this: due to the option 
> listambiguous being set by default nowadays trying to complete an
> empty string will indeed have no visual result in many cases. So you
> might want to have a look at the description of options like
> listambiguous, autolist, automenu, etc.
> 
> Bye
>  Sven
> 
> 
> --
> Sven Wischnowsky                         wischnow@informatik.hu-berlin.de
> 

-- 
Josh Howard <jrh@vicor-nb.com>


  reply	other threads:[~1999-03-23 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-23 13:46 Sven Wischnowsky
1999-03-23 18:27 ` Josh Howard [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-23  1:39 Josh Howard
1999-03-23  9:07 ` 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=yfg1zigqcxm.fsf@kashmir.vicor-nb.com \
    --to=jrh@kashmir.vicor-nb.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).