help / color / Atom feed
From: Peng Yu <pengyu.ut@gmail.com>
To: Tom Boyd <tvboyd23@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Is it worthwhile to use oh-my-zsh?
Date: Fri, 6 Sep 2019 14:33:31 -0500
Message-ID: <CABrM6wmXC7OSFDZFBY8wS0pxRB5Z7bz_DDKzQR1nky9CO5ggGQ@mail.gmail.com> (raw)
In-Reply-To: <CAO1rNLj9YA+4a+5SV+PURsfPJXNm8xY45i6kbrsPpF2NFY1fsg@mail.gmail.com>

I just tried it. I commented out this in my ~/.zshrc.

In a .git repo, it shows the git branch and the basename of the parent
directory. But this is not the formation that I need. I almost always
in the master branch, in which case I don't care showing the branch
name. I have many directory with the same basename, just showing the
basename of my currently is not informative.

How to get rid off these features?

On 9/6/19, Tom Boyd <tvboyd23@gmail.com> wrote:
> Yes very much so. Omz is tremendously powerful and is loaded with features
> that completely change the game in terms of productivity. Once you start
> using it it's actually really hard to go back once you've got the common
> usage in muscle memory. I've never had any issues with sluggishness either,
> with the config I currently have I find it just as fast as vanilla zsh.
> On Fri, Sep 6, 2019, 2:38 PM Peng Yu <pengyu.ut@gmail.com> wrote:
>> Hi,
>> I just have a vanilla ~/.zshrc. I'd like something essential things
>> like PS1 set to my pwd and hostname, etc. I saw people use things like
>> oh-my-zsh to make some fancy things like showing git branches, etc.,
>> if in a git repo. But if I remember it correctly, it could cause a
>> little sluggish that can be sensed.
>> So if I just want something essential, and not to want to feel any
>> sluggishness, I'd better just configure ~/.zshrc on my own without
>> using things like oh-my-zsh configured by others.
>> --
>> Regards,
>> Peng


  parent reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 18:37 Peng Yu
     [not found] ` <CAO1rNLj9YA+4a+5SV+PURsfPJXNm8xY45i6kbrsPpF2NFY1fsg@mail.gmail.com>
2019-09-06 19:33   ` Peng Yu [this message]
2019-09-07  0:43     ` Danh Doan
2019-09-07  0:49       ` Yaro Kasear
2019-09-07  1:40       ` Peng Yu
2019-09-07  1:59         ` Danh Doan
2019-09-07 12:22       ` Daniel Shahaf
2019-09-07 13:58 ` Roman Perepelitsa
2019-09-07 20:18   ` Frank Terbeck
2019-09-08  0:33     ` Bart Schaefer
2019-09-08 15:41       ` Roman Perepelitsa
2019-09-08 19:05         ` Nick Cross
2019-09-08 19:41           ` Roman Perepelitsa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABrM6wmXC7OSFDZFBY8wS0pxRB5Z7bz_DDKzQR1nky9CO5ggGQ@mail.gmail.com \
    --to=pengyu.ut@gmail.com \
    --cc=tvboyd23@gmail.com \
    --cc=zsh-users@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link


Archives are clonable: git clone --mirror http://inbox.vuxu.org/zsh-users

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git