zsh-users
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-users@zsh.org
Subject: Re: zsh-newuser-install
Date: Thu, 24 Apr 2014 18:02:15 +0200	[thread overview]
Message-ID: <ljbci7$l4t$1@ger.gmane.org> (raw)
In-Reply-To: <535920E5.1090108@eastlink.ca>

On 04/24/2014 04:34 PM, Ray Andrews wrote:
>> If nobody used oh-my-zsh, the world would be a better place. Or at
>> least #zsh would be.
>> I had to smile at this :)
>> But, sadly, many of the people that I know use it.
> 
> Indeed? What's wrong with it? When I was looking for reliable 
> help/information about zsh
> I remember seeing it, tho all I remember is that it seemed very advanced 
> and complicated,
> but what is 'sad' about people using it?  Too bad there isn't some sort 
> of overview of all zsh
> resources, so that one knows where to look for information, and what to 
> expect here and there.

The problem is that it is, indeed, quite complicated. It's not exactly
what I would recommend to somebody that is starting from zero with zsh.

Debugging slow completion or any issue you have with it will immediately
be too hard for somebody who never tweaked zsh before, because there's
no single "item" you can search for in the manual page.

For instance, I severely dislike when completion tries to outsmart me,
or behaves in non-predictive ways. I care much more that completion
takes 0 time (as in: no perceptible time) to complete. You'll need some
RTFM to tweak the completer in the way you want, but tweaking oh-my-zsh
will just be harder.

I see no difference between bash/zsh if I really wanted to use just some
pre-packaged config. You can roughly get the same behavior anyway.



  reply	other threads:[~2014-04-24 16: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                   ` Yuri D'Elia [this message]
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='ljbci7$l4t$1@ger.gmane.org' \
    --to=wavexx@thregr.org \
    --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).