From: shawn wilson <ag4ve.us@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: setopt interactivecomments
Date: Thu, 17 Apr 2014 19:51:45 -0400 [thread overview]
Message-ID: <CAH_OBidqAPAipRNVgDaC=TRwN_7p1H4TWb3zq5m54V0USUKHKg@mail.gmail.com> (raw)
In-Reply-To: <140417154855.ZM22920@torch.brasslantern.com>
On Thu, Apr 17, 2014 at 6:48 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Apr 17, 6:07pm, shawn wilson wrote:
> }
> } 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.
>
> How does that make sense? If you want "as close to what sh does by
> default" just *use bash*, don't reconfigure things that aren't bash.
>
> Unless for some reason you can't install bash, which is why zsh behaves
> differently if you name it "sh" instead, so you don't have to worry
> about otherwise mucking its configuration to make it bash-like.
I use zsh because of the zle stuff and (much better) completion and
OMZ and other stuff. I still expect it to behave a certain way.
Basically, I like it for my main shell because I can twist it in ways
that would be much harder (or impossible) in bash (and because BashIt
has a way to go before they're near OMZ).
next prev parent reply other threads:[~2014-04-17 23:52 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
2014-04-17 22:48 ` Bart Schaefer
2014-04-17 23:51 ` shawn wilson [this message]
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_OBidqAPAipRNVgDaC=TRwN_7p1H4TWb3zq5m54V0USUKHKg@mail.gmail.com' \
--to=ag4ve.us@gmail.com \
--cc=schaefer@brasslantern.com \
--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).