zsh-users
 help / color / mirror / code / Atom feed
From: shawn wilson <ag4ve.us@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: setopt interactivecomments
Date: Thu, 17 Apr 2014 18:07:43 -0400	[thread overview]
Message-ID: <CAH_OBiczp40H=mbquk248g0EQdnZrjWi1tZ0zP4iWrCyy5mjUg@mail.gmail.com> (raw)
In-Reply-To: <5350494F.6070003@eastlink.ca>

On Thu, Apr 17, 2014 at 5:36 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> On 04/17/2014 12:37 PM, Bart Schaefer wrote:
>

>>
>> What did eventually happen after the mess was cleaned up is that the
>> zsh-newuser-install system got created.  It could use an update, but
>> is intended to walk you through enabling the stuff that you're most
>> likely to want.
>
> Sounds exactly right. I seem to have missed it.
>

I think that's reasonable - it's been a while since I've generated a new config.

>>
>> [*] I use the term "we" loosely because I personally quit working on zsh
>> for a couple of years until sanity had been restored.
>
> Well, sanity matters. I take a rather conservative view  on most things
> myself, but at the
> same time, I think a few things are now so bedrock standard that we can
> safely part with
> the traditions of 20 years ago on some issues. What, really, would break if
> the backspace
> was enabled by default? What would break if interactive comments was on by
> default? Who
> would complain? Does anyone on Earth really not want command recall?
>

I kinda like nothing being enabled except in config - package sane
configs to be /etc/zsh/* (or /usr/local/etc/zsh/ on BSD I suppose) and
the new-user script sounds like the right way. This is only the second
time something has seemed weird (or from what I wouldn't expect) in
zsh (the other being how arrays are expanded - as arrays are broken or
near enough to broken in bash, I have no complaints about any
improvements zsh makes with them).

As for this (and other 'features') I suppose I'd expect package
maintainers in Linux to make it as close to what you'd get in bash as
possible and the core package to come with configs to get as close to
what sh does by default.


  reply	other threads:[~2014-04-17 22:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 14:35 shawn wilson
2014-04-16 17:27 ` Bart Schaefer
2014-04-16 17:37   ` shawn wilson
2014-04-17 14:37     ` Ray Andrews
2014-04-17 19:37       ` Bart Schaefer
2014-04-17 21:36         ` Ray Andrews
2014-04-17 22:07           ` shawn wilson [this message]
2014-04-17 22:48             ` Bart Schaefer
2014-04-17 23:51               ` shawn wilson
2014-04-17 22:41           ` Bart Schaefer
2014-04-18  3:10             ` Ray Andrews
2014-04-18 11:59             ` Roman Neuhauser
2014-04-23 15:50         ` zsh-newuser-install Peter Stephenson
2014-04-23 20:31           ` zsh-newuser-install Yuri D'Elia
2014-04-23 23:53             ` zsh-newuser-install Mikael Magnusson
2014-04-24  6:23               ` zsh-newuser-install Yuri D'Elia
2014-04-24 14:34                 ` zsh-newuser-install Ray Andrews
2014-04-24 16:02                   ` zsh-newuser-install Yuri D'Elia
2014-04-25  1:38                     ` zsh-newuser-install Ray Andrews
2014-04-24 16:04                   ` zsh-newuser-install Axel Beckert
2014-04-25 15:43               ` zsh-newuser-install Martin Vaeth
2014-04-25 16:21                 ` zsh-newuser-install Peter Stephenson
2014-04-26 10:07                   ` zsh-newuser-install Martin Vaeth
2014-04-26 20:21                     ` zsh-newuser-install Peter Stephenson
2014-04-26 20:38                     ` zsh-newuser-install Bart Schaefer
2014-04-25 17:03                 ` zsh-newuser-install Bart Schaefer
2014-04-26 13:49                 ` zsh-newuser-install Yuri D'Elia
2014-04-26 21:10                   ` zsh-newuser-install Bart Schaefer
2014-04-28 17:35                     ` zsh-newuser-install Bart Schaefer
2014-04-24  1:05           ` zsh-newuser-install Ray Andrews
2014-04-17 19:04     ` setopt interactivecomments 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='CAH_OBiczp40H=mbquk248g0EQdnZrjWi1tZ0zP4iWrCyy5mjUg@mail.gmail.com' \
    --to=ag4ve.us@gmail.com \
    --cc=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).