From owner-freebsd-questions@FreeBSD.ORG Sun Jun 7 04:32:42 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9A5F1065670 for ; Sun, 7 Jun 2009 04:32:42 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5AEB98FC0A for ; Sun, 7 Jun 2009 04:32:42 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so1297861qwe.7 for ; Sat, 06 Jun 2009 21:32:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bq6b7oEiKjN0kG+L4UROAUl412mkHA3MiiAyZTZHfHg=; b=iYwIfZ0A2ZFFttOYOUXojf/2ZaUSHBf4Wz+y3EXBKz0QSKxKSrhK8eY+U3osgD76E1 Og9QViQMHguYwG+ITSzjqCIWfik0A25I+GS20Zkbu3LYPg6Nha2m9QmncDq3RKvtEtsj l2T7Q4LnJHDj65v5N9vXK6eqA8mYxhlzgZRhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QLc/qRmlACysrJfaOLRw4t6N02dvHAv07pBlzhKB6LGlcEY/4W2hwm7fh2SD/ZJt7C i1rJVOHuDruTQEenzeS/DsrcdAx7sCfdvHvpZkrxeAxmdJ/Y6D1HfNsFSi+UZ73oll7+ 8IlENki4ks7PeVfH6UqU+eiJ7h6y1KArP2/KU= MIME-Version: 1.0 Received: by 10.220.80.134 with SMTP id t6mr3004892vck.108.1244349161503; Sat, 06 Jun 2009 21:32:41 -0700 (PDT) In-Reply-To: References: <200906050924.23167.kirk@strauser.com> <200906051208.43135.kirk@strauser.com> <4A29EBB7.9090100@strauser.com> <20090606094648.GA10672@ei.bzerk.org> Date: Sat, 6 Jun 2009 22:32:40 -0600 Message-ID: From: Tim Judd To: utisoft@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Date representation as YY/DDD or YYYY/DDD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jun 2009 04:32:43 -0000 On 6/6/09, Chris Rees wrote: > 2009/6/6 Wojciech Puchar : >>>> what some single-letter option meant. I pretty much never use them on >>>> the command line, though. >>> >>> Agreed, the long options *as an alternative* can be descriptive in >>> scripts, >>> tutorials, howto's etc. >>> The other reason often mentioned, there being not enough letters in the >>> alphabet to cover all possible options, in my opinion advocates bloated >>> software (one program can do it all), which goes against the Unix >>> paradigm >>> of making small programs that do one task exceptionally well and just >>> chaining these together. >> >> you exaggerate a bit. >> >> for example rsync does have >26 options but most make sense for program >> that >> is dedicated to one task, and it isn't against Unix paradigm. >> >> But it have one letter shortcuts for mostly used parameters >> > > Can I be picky and point out it's actually 52 short options? > > [chris@amnesiac]~% ls -f > quantumdot mail cromwell_1024.bin.gz > public_html bnreg amnesiackey.pub > backup.sh.gz cromwell.bin.gz check-portupgrade.pl > why.c teamspeak > [chris@amnesiac]~% ls -F > amnesiackey.pub cromwell.bin.gz quantumdot/ > backup.sh.gz cromwell_1024.bin.gz teamspeak/ > bnreg/ mail/ why.c > check-portupgrade.pl public_html/ > [chris@amnesiac]~% > > for just one example.... > > Chris and digits add another 10. We're up to 62 single-character options. I'm sure punctuation will be next. dig www.google.com @192.168.0.1 OK, so now where does that leave us?