Date: Thu, 19 Jan 2012 20:31:36 +0100 From: Jilles Tjoelker <jilles@stack.nl> To: Matthew Story <matthewstory@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: intent of tab-completion in /bin/sh in 9.0 Message-ID: <20120119193135.GA5955@stack.nl> In-Reply-To: <CAB%2B9ogewjp4r8oyhAF5M9ofdvQR3KrJQaDOZKuZoVTu%2Br-1jWg@mail.gmail.com> References: <CAB%2B9ogffj6XOTrJrZACVUdzoJTnBf6s03up3N%2BpSC4_71V2=Jg@mail.gmail.com> <20120118221630.GA97471@stack.nl> <CAB%2B9ogewjp4r8oyhAF5M9ofdvQR3KrJQaDOZKuZoVTu%2Br-1jWg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 18, 2012 at 08:46:18PM -0500, Matthew Story wrote: > On Wed, Jan 18, 2012 at 5:16 PM, Jilles Tjoelker <jilles@stack.nl> wrote: > > POSIX itself has gradually adopted ksh features, so seeing more of them > > in future is not unlikely. Most of the new language features in 9.0 are > > either from POSIX.1-2008 or on the roadmap for a new version of POSIX > > (in collaboration with other shell authors). > Tab completion is a welcome addition, I was unaware that this had been (or > is slated to be) added to the POSIX specification. This makes far more > sense than my proposed explanations. Thanks for the clarification. Tab completion is not in POSIX and not planned to be (as far as I know), although there is some fairly ugly pathname completion functionality required in 'set -o vi' mode (we do not implement it). The reason is more like that I noticed that NetBSD had it and found someone willing to port it and add some small features (escaping special characters in what is inserted). In using /bin/sh as login shell on virtual machines (to avoid the need to install something else from ports), I have found the filename completion to be remarkably useful. -- Jilles Tjoelker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120119193135.GA5955>