zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: symlink chain.
Date: Sun, 04 Jan 2015 20:24:14 -0800	[thread overview]
Message-ID: <54AA11EE.2000900@eastlink.ca> (raw)
In-Reply-To: <BF111510-8BED-426D-A7F0-89455369759A@larryv.me>

On 01/04/2015 06:28 PM, Lawrence Velázquez wrote:
> On Jan 4, 2015, at 8:34 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
>> On Jan 4, 12:49pm, Ray Andrews wrote:
>> }
>> } But, would we not agree that it is the natural thing to prefer
>> } cumulative switches over limiting switches?  Is it not intuitive that
>> } as you 'add' switches you 'add' features?
>>
>> There's no answer for this that fits all cases.  In an ideal world,
>> one would always think of the minimal action and then build on it,
>> but the world is rarely ideal.  More often there exists something
>> that has a purpose or mechanism very similar to a new idea, and so
>> that something is altered to support the new idea.  A lot of times,
>> that isn't an additive process.
> Also consider an alternate (and equally valid) point of view in which
> commands should be a sort of variable-length encoding. That is, the
> shortest commands (the ones without switches) would ideally represent
> *common* actions, not necessarily *minimal* actions.
>
> vq
Yes.  We always are stuck with the limits of language there, but there's 
no doubt that the 'nix world has attempted to do just that. The common 
commands are normally, what? four letters or fewer.
>


  reply	other threads:[~2015-01-05  4:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27  4:50 Ray Andrews
2014-12-27 23:38 ` Ray Andrews
2015-01-02 17:03 ` Peter Stephenson
2015-01-02 18:42   ` Ray Andrews
2015-01-02 20:27     ` Lawrence Velázquez
2015-01-02 21:19       ` Ray Andrews
2015-01-02 21:24     ` Peter Stephenson
2015-01-02 21:36       ` Ray Andrews
2015-01-02 21:53       ` Ray Andrews
2015-01-02 22:21         ` Peter Stephenson
2015-01-02 23:42           ` Ray Andrews
2015-01-03  1:08             ` Ray Andrews
2015-01-03  5:03               ` Bart Schaefer
2015-01-03  5:53                 ` Ray Andrews
2015-01-03  7:17                   ` Bart Schaefer
2015-01-03 17:14                     ` Ray Andrews
2015-01-03 20:02                       ` Bart Schaefer
2015-01-03 21:13                         ` Ray Andrews
2015-01-03 21:42                           ` Peter Stephenson
2015-01-03 22:42                             ` Ray Andrews
2015-01-04  0:41                               ` Bart Schaefer
2015-01-04  3:45                                 ` Ray Andrews
2015-01-04  0:40                           ` Bart Schaefer
2015-01-04  3:35                             ` Ray Andrews
2015-01-04  8:31                               ` Bart Schaefer
2015-01-04 20:49                                 ` Ray Andrews
2015-01-05  1:34                                   ` Bart Schaefer
2015-01-05  2:28                                     ` Lawrence Velázquez
2015-01-05  4:24                                       ` Ray Andrews [this message]
2015-01-02 22:22         ` Bart Schaefer

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=54AA11EE.2000900@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    /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).