3 ms·
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 o
by CJefferson 11y ago
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).
- dmix 11y agoThanks for the heads up, looks like I'll pass on prezto...
- jzelinskie 11y agoI write scripts in bash, because most people probably aren't using zsh or have zsh installed. Also, when you feel like losing the magic, you can escape commands by prefixing them with backslash (i.e. \cat vs cat).
- dguaraglia 11y agoOh god, I still swear at the whole "\rm" thing. I guess it's been a benefit a couple times where I might have deleted something by accident, but considering I mostly work on Git repositories, the inconvenience added by the wrappers is totally not worth it.
- jeffcox 11y agoIt'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.
- MetaCosm 11y agoGenerally 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.
- CJefferson 11y agoIf 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.
- jeffcox 11y agoYou'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.