From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: zsh-newuser-install
Date: Fri, 25 Apr 2014 10:03:16 -0700 [thread overview]
Message-ID: <140425100316.ZM12397@torch.brasslantern.com> (raw)
In-Reply-To: <slrnlll0kq.v0i.martin@lounge.imp.fu-berlin.de>
On Apr 25, 3:43pm, Martin Vaeth wrote:
}
} I understand that most features are off by default to keep
} compatibility. However, in interactive shells compatbility
} is not really an issue. Perhaps one could enable much more
} *interactive* features by default which are actually the
} biggest selling point of zsh.
Unfortunately you're wrong about this. Changing what is on by default
means that anyone who does NOT use/want a particular feature now has
to update their configuration to explicitly disable it. Avoiding this
kind of surprise has always been one of our goals.
} At least, some zshrc could be shipped which enables lots
} of these features
Cf. PWS reply to this.
} Some examples not mentioned yet by others:
}
} zstyle ':completion:*' format '%B(%d)%b'
} zstyle ':completion:*' verbose true
Styles are something that would have to be enabled by sourcing a file,
I don't think we want to pack loads of these strings into a module
(especially since the ":completion:..." naming scheme is a convention
entirely created by the shell functions in the Completion/ tree).
We could probably add some zstlye commands to compinit, using the usual
paradigm of testing for the existence of the style before setting it:
zstyle -m ':completion:*' format '*' ||
zstyle ':completion:*' format '%B(%d)%b'
Etc.
next prev parent reply other threads:[~2014-04-25 17:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:35 setopt interactivecomments 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
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 ` Bart Schaefer [this message]
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=140425100316.ZM12397@torch.brasslantern.com \
--to=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).