5 ms·

> Projects like oh-my-zsh are nice because they provide a much richer default that lazy folks like me can use without ever having to know or care about how to a

by kbd 11y ago

> Projects like oh-my-zsh are nice because they provide a much richer default that lazy folks like me can use without ever having to know or care about how to actually configure a shell because the alternative is that I just won't do it. Thanks for giving me a different perspective. For me, it bugs me to not know what's built-in vs what's configuration. For example, I recently discovered that option+arrow key to skip back/forward words was an OSX Terminal feature when it didn't work in iTerm2. So I configured it to work how I wanted in my .inputrc and now it should work everywhere. Starting with the defaults and changing things as you get an itch to scratch seems like a better way to learn long-term, but I can see just wanting use someone's template and be done with it. I guess it's the difference between frameworks and libraries, and between people who use someone's addon pack in World of Warcraft vs just using a few addons and designing their own UI.

jacobolus 11y ago
Actually ⌥← / ⌥→ to move by words is a feature built into the Cocoa text system. It will work in any standard text box in any OS X app. You can also use ⌥⌫ to delete by words. Other default key bindings: http://www.hcs.harvard.edu/~jrus/site/system-bindings.html http://www.hcs.harvard.edu/~jrus/site/system-bindings.html
- kbd 11y ago
  > is a feature built into the Cocoa text system Well, yes, thanks. So it arguably should have worked in iTerm2 to start with. In any case, now with the same configuration it'll even work on Linux (I also configured ctrl+left and right to work the same for non-⌥-having keyboards). And my point remains the same, that I learned what was OSX, what was bash, and what was readline, more about how to configure readline, that you can 'cat' with no arguments and type things to see their escape codes (which is how I got ^[^[[C and ^[^[[D as the codes for ⌥← / ⌥→), that \e is short for the escape part ^[ (though I still don't understand how escape codes work everywhere, more learning to do). All because something didn't work how I wanted. Of course it'd be nice if readline had better defaults too :)
  - roddds 11y ago
    Could you share the relevant part of your config and some rough instructions on how to set it up? I just got my first mac a few days ago and I'm tearing my hair out here.

by kbd 11y ago

jacobolus 11y ago

Actually ⌥← / ⌥→ to move by words is a feature built into the Cocoa text system. It will work in any standard text box in any OS X app. You can also use ⌥⌫ to delete by words. Other default key bindings: http://www.hcs.harvard.edu/~jrus/site/system-bindings.html http://www.hcs.harvard.edu/~jrus/site/system-bindings.html

kbd 11y ago
> is a feature built into the Cocoa text system Well, yes, thanks. So it arguably should have worked in iTerm2 to start with. In any case, now with the same configuration it'll even work on Linux (I also configured ctrl+left and right to work the same for non-⌥-having keyboards). And my point remains the same, that I learned what was OSX, what was bash, and what was readline, more about how to configure readline, that you can 'cat' with no arguments and type things to see their escape codes (which is how I got ^[^[[C and ^[^[[D as the codes for ⌥← / ⌥→), that \e is short for the escape part ^[ (though I still don't understand how escape codes work everywhere, more learning to do). All because something didn't work how I wanted. Of course it'd be nice if readline had better defaults too :)
- roddds 11y ago
  Could you share the relevant part of your config and some rough instructions on how to set it up? I just got my first mac a few days ago and I'm tearing my hair out here.