From: Doug Kearns <dougkearns@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: new shells completion type
Date: Thu, 23 Jun 2005 01:04:49 +1000 [thread overview]
Message-ID: <20050622150449.GD4591@localhost.localdomain> (raw)
In-Reply-To: <9002.1119448760@trentino.groupinfra.com>
On Wed, Jun 22, 2005 at 03:59:20PM +0200, Oliver Kiddle wrote:
> Doug Kearns wrote:
> > Here is a new completion type for shells. It seems to me that if we're
> > going to complete shells from /etc/shells then it should be restricted
> > _only_ to shells listed there. This will change the behaviour of useradd
> > completion which always included /bin/false.
>
> With useradd/usermod, it's very useful to have /bin/false as a match. If
> the user account won't need to login then that's a common way to ensure
> it can't.
Right, but it was my understanding that these commands were supposed to
check /etc/shells, if it existed, and fail if the shell arg isn't listed
there. Also, that /bin/false was generally added to this file if it was
required. However, a quick check on my system suggests that although
chsh does behave as described above useradd/usermod do not...
> > - '-s[shell to execute rather than $SHELL]:shell name: _command_names -e' \
> > + '-s[shell to execute rather than $SHELL]:shell:_shells' \
>
> I don't use screen but does that option only get used with actual
> shells?
I think you're right the definition of 'shell' may well be less strict
than that - I'll have a look.
<snip>
Regards,
Doug
next prev parent reply other threads:[~2005-06-22 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 13:11 Doug Kearns
2005-06-22 13:59 ` Oliver Kiddle
2005-06-22 15:04 ` Doug Kearns [this message]
2005-06-22 14:07 ` Stephane Chazelas
2005-06-22 14:18 ` Peter Stephenson
2005-06-22 14:42 ` Oliver Kiddle
2005-06-23 10:12 ` Doug Kearns
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=20050622150449.GD4591@localhost.localdomain \
--to=dougkearns@gmail.com \
--cc=zsh-workers@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).