Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: setopt interactivecomments
- X-seq: zsh-users 18724
- From: shawn wilson <ag4ve.us@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: setopt interactivecomments
- Date: Wed, 16 Apr 2014 13:37:57 -0400
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kSlNYPI/h5KE1ILHmaMmV5f3rNEq/AvyKHH2E2qb8L4=; b=P9YF+W6ydccigbFkOd0yw/qSUItE7CwrUUs7SX9pUmI/6hhifUnWisMZaJN8TNMrZx FxKY8l40WORQ0UGOTyEPF0ANKXMOL+ZAY0gvaAe6JVNrrW7kR6e884c3ZhHToSuBLNuC CTNScP9qTCyiB3IPTC/kEO8OetV5nKEYhO7WMZkguDcwvU3lF0CsRSXfUQuOjCRjef9T pgTuutB2siwleInfcS8aLHhRWf9WVsi6irxAbToSAjNYL78v5zJA7HMVffz3Jp9lYmfW sVI1bTGeLK/EfNdU/fG3bvzlscxVOqZTC8hBsk6EA3RPiS6MadmADYXVqD8H4U9vhFvK aTaw==
- In-reply-to: <140416102727.ZM19090@torch.brasslantern.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAH_OBicpVKS-URnd-Gq=gj+qc6OhDCqf0mgDfVcda27mEEfUKg@mail.gmail.com> <140416102727.ZM19090@torch.brasslantern.com>
On Wed, Apr 16, 2014 at 1:27 PM, Bart Schaefer
<schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Apr 16, 10:35am, shawn wilson wrote:
> }
> } Why is this feature disabled by default - it seems like enabling and
> } allowing it to be disabled (since the behavior works in other shells)
> } would be the correct way to do things?
>
> It's disabled because it always has been, and therefore enabling it might
> break longstanding usage.
>
> It has always been disabled because zsh originated as a way to bring
> Bourne shell syntax to students who had been introduced to BSD Unix
> via [t]csh, and csh does not have interactive comments. A lot of the
> default behaviors and interactive design of zsh derive from Paul Falstad
> (the original author) making subjective judgements about what were the
> best features of csh and sh, rather than about what features were the
> most common in other sh clones.
So if I want to know what ideas are based on, I should refer to how
FBSD tcsh and sh behave and not how Bash on Linux functions? Or as far
as this type of thing is concerned, it would stay either way because
it was an original implementation decision? (obviously, because of the
former, the later becomes moot, but I'm curious what the current
mindset of development is)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author