dyanaraps

12 ms·

1. 31.▲
   by dyanaraps 7y ago

   Off the top of my head, a few notable things I've learned: - Safely working with "string lists" (list="el el el el"). - Filtering out duplicate items. - Reversing the list. - etc. - Using `case` t
2. 32.▲
   by dyanaraps 7y ago

   This is really neat, thanks for sharing.
3. 33.▲
   by dyanaraps 7y ago

   Thanks! Fancy seeing you here. :)
4. 34.▲
   by dyanaraps 7y ago

   The shell is my favorite language and I really don't know why. It's definitely possible to write shell code which properly passes shellcheck's linter though it's an uphill battle to learn the ins and outs and _why_ X is
5. 35.▲
   by dyanaraps 7y ago

   I've been meaning to get around to it. I hadn't messed around with /dev/tcp prior to writing this bible. I've since implemented a very bare-bones and very featureless IRC client using /dev/tcp and bash. h
6. 36.▲
   by dyanaraps 7y ago

   I understand your concerns about bash features and POSIX compatibility. The bash bible was written specifically to document the shell extensions bash implements. My focus for the past few months has been writing a Linux distribution (and it
7. 37.▲
   by dyanaraps 7y ago

   Hello, I'm the author of the Pure Bash Bible. Happy to answer any questions you may have. Here's an example of what bash is capable of: https://github.com/dylanaraps/fff/ (a TUI file manager written in b
8. 38.▲
   by dyanaraps 7y ago

   Hello, I'm the creator of KISS and I'm happy to answer any questions anyone may have. For the code itself: - https://github.com/kisslinux KISS on repology.org: - https://repology.org/repository&#x2