home.social

Search

1000 results for “DrHyde”

  1. I've been playing with as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value , , etc. I agree that some ways of using for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

  2. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  3. Grargh! hates extensions. And can't be configured to specifically use instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

  4. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  5. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  6. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  7. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  8. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

  9. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  10. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  11. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  12. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the format which is standardised in ITU-T . The request is in Github issue 164!

    github.com/DrHyde/perl-modules

  13. Re earlier toot ... as soon as I'd finished dealing with 's PRs, I wanted to use the script to view other peoples' PRs against my code (there are only two that I've not dealt with because I'm a good boy, although one has been festering for 7 years because I'm a bad boy), and then to see all my PRs against other peoples' code that are still open. And so the script got just a teensy bit bigger.

    github.com/DrHyde/shellscripts

  14. Re earlier toot (fosstodon.org/@DrHyde/11517952) the release was further delayed by being bastards and breaking my CI by not letting me grab their data from within workflows, so I had to work around that. So that's more crawling horrors accreted onto the 20 years old that builds it all. Yay! But we have a release! The only changes are data updates and a tweak to cope with the 's new weirdness.

    @perl

  15. @DrHyde @bmop So glad to see you’ve joined the Odyssey! We’re particularly proud of this collection of #opera collabs with @bmop because they’re all #worldpremiere recordings.

  16. @DrHyde On behalf of us all, I apologise for our failure. You are right, that is very lax from us.

    I, of course, will be indulging in lots of during the coming weeks.

  17. @DrHyde Okay, my try:

    #WPE is making a fortune of the open-source software #WordPress, without giving back and abusing trademarks. But by defending his legacy, @photomatt has also decided to act like a bully. And his behaviour hurts parts of the WP community - esp. people who make money with wpe. Furthermore, it became a lawsuit so lawyers decide about actions.

    And what we know from the lunch hall, 🇿🇦 or 🇺🇦, you do not defend a bully like Chamberlain, but as Churchill (I‘m German)

  18. RE: fosstodon.org/@DrHyde/11577485

    Arising from this ... overnight, shat approximately 15,000 pull requests at me, all of which I needed to look at. I could have written a small script to parse them all out of my mailbox, but a script that uses 's CLI tool and API is always gonna be more reliable. github.com/DrHyde/shellscripts

    Version 2 might save me having to look at them, by only showing me PRs which touch unexpected files or have test failures, and just auto-merge the rest. Need to look at the API in more depth.

  19. @DrHyde You would not believe what you can do under a dissecting microscope with a pair of very sharp forceps in one hand and a human eyelash wand in the other.

    I taught a room full of undergraduates to repeat these classic experiments in one afternoon in 1999.

    pmc.ncbi.nlm.nih.gov/articles/

  20. @DrHyde

    I had handfuls of #leaflets from the lefty candidate standing against #starmer in Holborn - they all went in the bin

    does anyone read these leaflets

  21. @DrHyde

    I had handfuls of #leaflets from the lefty candidate standing against #starmer in Holborn - they all went in the bin

    does anyone read these leaflets

  22. @DrHyde

    I had handfuls of #leaflets from the lefty candidate standing against #starmer in Holborn - they all went in the bin

    does anyone read these leaflets

  23. @DrHyde

    I had handfuls of #leaflets from the lefty candidate standing against #starmer in Holborn - they all went in the bin

    does anyone read these leaflets

  24. @DrHyde

    I had handfuls of #leaflets from the lefty candidate standing against #starmer in Holborn - they all went in the bin

    does anyone read these leaflets

  25. For anyone willing to peer into the abyss ... github.com/DrHyde/shellscripts

    Instead of running three other scripts (each of which is a wrapper around `ffmpeg`) in turn, it now runs them in parallel, capturing the results, and then spitting out the results consistently no matter in what order the individual scripts finished.

    I think in this would be called / or some such. Normal devs just call it "programming".

  26. @DrHyde Oh, I think I know that feeling; my sympathies.

    I am much happier with using for my personal needs on a home server.

    I usually describe it as a DIY CI: it allows one to build the CI solution they need, instead of fitting their needs to their CI solution.

    Sure, it is a different kind of tinkering, but I thought it might be of interest for you too.

    laminar.ohwg.net/

  27. @DrHyde I suppose you (along with the #ModernLibrary) prefer #JamesJoyce? newideal.aynrand.org/a-tale-of

    The list from that editorial (sites.prh.com/modern-library-t) had a solicited correspondence from what’s now the Columbia Publishing Course. The latter’s director said at the time, “Our list reflects a young, more #feminist crowd. [It] shows a difference of age and taste.”

    #AynRand’s #TheFountainhead was #43 and #AtlasShrugged was #92: thecrimson.com/article/1998/7/