zsh-workers
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-workers@zsh.org
Subject: Re: off topic
Date: Fri, 09 Dec 2016 21:12:44 +0100	[thread overview]
Message-ID: <874m2cc14z.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <62522.1481300922__19313.1602755331$1481301401$gmane$org@hydra.kiddle.eu>

On Fri, Dec 09 2016, Oliver Kiddle wrote:
> There's clear advantages to having a powerful setup that you understand
> well. If that process now involves "brutality" then you can understand
> why people might be be happy to just take what they get with oh-my-zsh:
> and I don't view that as heresy.

Maybe people seem to think that reading the actual [lengthy]
documentation is "brutality" ;)

I pretty much share the same views as Oliver on that front.
And I'm pretty sure this was discussed before.

But it can provide a showcase of features you might want to enable,
which is a good thing. Sometimes you don't know a feature existed until
you see it, as there are just too many of them. Plus, some people
really, _really_ like prompt-bling!

There are certainly zsh users out there that just want that, and are
fine with whatever TAB does by default.


       reply	other threads:[~2016-12-09 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161209122958.GD19559@256bit.org>
     [not found] ` <57127.1481294647@hydra.kiddle.eu>
     [not found]   ` <584AC8AC.9050406@eastlink.ca>
     [not found]     ` <62522.1481300922__19313.1602755331$1481301401$gmane$org@hydra.kiddle.eu>
2016-12-09 20:12       ` Yuri D'Elia [this message]
     [not found]     ` <62522.1481300922@hydra.kiddle.eu>
     [not found]       ` <584AEDBF.2050402__19991.0537027337$1481307418$gmane$org@eastlink.ca>
     [not found]         ` <20161209192406.GA27532@fujitsu.shahaf.local2>
2016-12-11 18:06           ` Peter Stephenson
2017-04-27 15:43 Sebastian Gniazdowski

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=874m2cc14z.fsf@wavexx.thregr.org \
    --to=wavexx@thregr.org \
    --cc=zsh-workers@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).