From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Duncan Sargeant <dunc@tartarus.uwa.edu.au>
Cc: dunc@ucc.gu.uwa.edu.au, zsh-users@math.gatech.edu
Subject: Re: bash like tab tab 's
Date: Tue, 27 Aug 1996 02:48:31 -0700 [thread overview]
Message-ID: <960827024831.ZM6829@candle.brasslantern.com> (raw)
In-Reply-To: Duncan Sargeant <dunc@tartarus.uwa.edu.au> "Re: bash like tab tab 's" (Aug 27, 5:31pm)
On Aug 27, 5:31pm, Duncan Sargeant wrote:
} Subject: Re: bash like tab tab 's
}
} > } I noticed bash's tab tab feature, where pressing tab once
} > } will try to complete a word as per usual, but if it can't, pressing it a
} > } second time will give a list of commands.
} >
} > I think you want
} >
} > setopt autolist listambiguous
}
} that's does a list after the first TAB. I was interested in having it
} complete as far as possible first, beep, then (after second TAB) list.
`setopt autolist` lists after the first tab on any ambiguous competion.
If you add `setopt listambiguous` then it completes as far as possible
and lists only if "as far as possible" means "no further".
This is as close as you can get; it saves you having to type the second
tab when the completion is immediately ambiguous, which is (partly) why
it works this way.
--
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"
next prev parent reply other threads:[~1996-08-27 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-27 8:34 Duncan Sargeant
1996-08-27 9:23 ` Bart Schaefer
1996-08-27 9:31 ` Duncan Sargeant
1996-08-27 9:48 ` Bart Schaefer [this message]
1996-08-27 18:53 ` 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=960827024831.ZM6829@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=dunc@tartarus.uwa.edu.au \
--cc=dunc@ucc.gu.uwa.edu.au \
--cc=schaefer@nbn.com \
--cc=zsh-users@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).