Live data from Hacker News

Oh My Zsh

ohmyz.sh

31–40 of 40 posts

Re: Oh My Zsh

#31

Earlier quoted context omitted.

I found prezto did too many things (replaced mkdir, cp, rm and ls with slightly incompatible wrappers for example). The worst was wrapping diff and make, both of which broke scripts I used. oh-my-zsh seems from my experience to be less eager to replace built-in functionality (although, I'm not an expert in either).

It's so bizarre to me that people would look at the base install of essentially dotfiles as canonical and unalterable. Fork Prezto and maintain your own version.

Generally the reason to go with such a kit is so you DO NOT have to do the maintenance... you gain the benefits of the community with little to no effort.

Re: Oh My Zsh

#32

Earlier quoted context omitted.

I found prezto did too many things (replaced mkdir, cp, rm and ls with slightly incompatible wrappers for example). The worst was wrapping diff and make, both of which broke scripts I used. oh-my-zsh seems from my experience to be less eager to replace built-in functionality (although, I'm not an expert in either).

It's so bizarre to me that people would look at the base install of essentially dotfiles as canonical and unalterable. Fork Prezto and maintain your own version.

If we were talking about a single file of up to 100 lines or so, I would agree. But presto is huge! I don't want to read the whole thing and decide what bits I do and don't want.

Re: Oh My Zsh

#33
Note that by using Oh My Zsh, you acknowledge the fact that you're willing to wait for 10 seconds to get a prompt when opening a terminal. Which to my experience can be annoying.

Re: Oh My Zsh

#35

"Your terminal never felt _this_ slow before."

I use oh-my-zsh on ArchLinux with termite. Starts instantly and is as fast as stock bash. I suppose that this is mainly an OS X issue.

I use oh-my-zsh on Arch and it takes ages to give me a prompt unless I Ctrl-C. For some reason this only happens the first time I open a terminal after logging on. Haven't got around to digging up the root cause yet.

Re: Oh My Zsh

#36

Earlier quoted context omitted.

I use oh-my-zsh on ArchLinux with termite. Starts instantly and is as fast as stock bash. I suppose that this is mainly an OS X issue.

I use oh-my-zsh on Arch and it takes ages to give me a prompt unless I Ctrl-C. For some reason this only happens the first time I open a terminal after logging on. Haven't got around to digging up the root cause yet.

The first time opening a terminal window also takes longer on my machine, but only a second or two not longer.

Re: Oh My Zsh

#37

Earlier quoted context omitted.

It's so bizarre to me that people would look at the base install of essentially dotfiles as canonical and unalterable. Fork Prezto and maintain your own version.

If we were talking about a single file of up to 100 lines or so, I would agree. But presto is huge! I don't want to read the whole thing and decide what bits I do and don't want.

You're really only going after the config files, though. .zpreztorc, and if you don't like some of Sorin's aliases (rm, ls, etc) you can take them out of the utility plugin. I've spent maybe an hour "working" on my fork in the last year.

Re: Oh My Zsh

#38

Really? Piping from curl/wget into sh? In this day and age? Tsk tsk.

Yes, really. Also really "brew install X". Also really download some binary and run it. Do you inspect every line of the source code of the every app you run on your computer? I don't.

well, there's a jump from make install/wgetting/brew install and just trusting your distro's repo (eg: Debian).

Re: Oh My Zsh

#39
I've never used zsh, so a sophisticated configuration for it would be a blind leap in a random direction, like e.g. Emacs Prelude. Instead, can anyone recommend good reference documentation about zsh configuration files? Going through all options and deciding how I want them is my preferred approach to configuring new software.

Re: Oh My Zsh

#40

Really? Piping from curl/wget into sh? In this day and age? Tsk tsk.

Yes, really. Also really "brew install X". Also really download some binary and run it. Do you inspect every line of the source code of the every app you run on your computer? I don't.

You're missing my point. Piping wget/curl into sh is notoriously dangerous not because of security concerns, but because of the behavior of sh if it only receives a partial script that way (such as would be the case if curl or wget are interrupted for whatever reason, particularly in the event of a network failure mid-download). At least with a package manager like Homebrew or apt-get it'll wait for the download to actually finish before trying to install something (at least on a per-package basis; few package managers actually wait for all packages and their dependencies to be downloaded before installing any of them).

Just because trendy hip tools like brew and RVM encourage this behavior doesn't mean it's actually a good idea.

Post reply on HN