home.social

#computerssuck — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #computerssuck, aggregated by home.social.

fetched live
  1. Ok, I've done updates, though unsure if they work anymore since the process stalls at 99%.
    My keyboard and mouse are back working, but it requires a docking station and an extension for the Logi receiver to do anything. (Neither are rationally justified.)

    I think I will stop using this Swearing Generator for the rest of the day.

    #Kubuntu #Legion #USBisBULLSHIT
    #Sonnettech #ComputersSuck

  2. Ok, I've done updates, though unsure if they work anymore since the process stalls at 99%.
    My keyboard and mouse are back working, but it requires a docking station and an extension for the Logi receiver to do anything. (Neither are rationally justified.)

    I think I will stop using this Swearing Generator for the rest of the day.

    #Kubuntu #Legion #USBisBULLSHIT
    #Sonnettech #ComputersSuck

  3. I can follow up on the `typeset -U` item.

    If you use `typeset -U` on an array tied to an environment variable, you will make a local copy of the array, which will be empty. It will then remove all the items from the env variable.

    So zsh intially has PATH (scalar, env) and path (array) tied. When you do `typeset -U path` in .zshrc, you trigger that effect. The right incantation is `typeset -TUx PATH path`. (Tied, Unique elements, and eXported.)

    #ComputersSuck

  4. I can follow up on the `typeset -U` item.

    If you use `typeset -U` on an array tied to an environment variable, you will make a local copy of the array, which will be empty. It will then remove all the items from the env variable.

    So zsh intially has PATH (scalar, env) and path (array) tied. When you do `typeset -U path` in .zshrc, you trigger that effect. The right incantation is `typeset -TUx PATH path`. (Tied, Unique elements, and eXported.)

    #ComputersSuck

  5. I didn't mention venvs or nix-shell. I have to figure out PATH for subshells in those two environments. I don't know exactly how that will work yet.

    Anyway, I have ranted. Thank you and good night.

    #ComputersSuck

  6. I didn't mention venvs or nix-shell. I have to figure out PATH for subshells in those two environments. I don't know exactly how that will work yet.

    Anyway, I have ranted. Thank you and good night.

    #ComputersSuck

  7. Here's a thing. Does this do what you expect? (I kind of did expect it, because I spent the whole day today reading the relevant sections of the zsh reference.)

    #ComputersSuck

  8. Here's a thing. Does this do what you expect? (I kind of did expect it, because I spent the whole day today reading the relevant sections of the zsh reference.)

    #ComputersSuck

  9. Is this sounding like a rant? It's feeling like a rant.

    Anyway, I have a strategy for collecting my path from its various sources and collating it into the best order. It will probably be a full day of debugging scripts. Because I have nothing better to do.

    I regret using zsh, and I regret using Home Manager. I may switch back to MacPorts some day. My MacBook is still on MacPorts.

    #ComputersSuck

  10. Is this sounding like a rant? It's feeling like a rant.

    Anyway, I have a strategy for collecting my path from its various sources and collating it into the best order. It will probably be a full day of debugging scripts. Because I have nothing better to do.

    I regret using zsh, and I regret using Home Manager. I may switch back to MacPorts some day. My MacBook is still on MacPorts.

    #ComputersSuck

  11. As best I can tell, `typeset -U` erases variables under certain circumstances.

    If you have a tied variable pair and you use -U on one half, both halves are unset. The zsh reference says not to do that, but Home Manager generates code that does that. To PATH/path. I never figured out what's going on; I took my dotfiles out of Home Manager and am now managing them myself.

    Which I need to, to untangle the path mess.

    #ComputersSuck

  12. As best I can tell, `typeset -U` erases variables under certain circumstances.

    If you have a tied variable pair and you use -U on one half, both halves are unset. The zsh reference says not to do that, but Home Manager generates code that does that. To PATH/path. I never figured out what's going on; I took my dotfiles out of Home Manager and am now managing them myself.

    Which I need to, to untangle the path mess.

    #ComputersSuck

  13. MacOS' default shell is zsh. I don't know why. The only advantage I've found is that it has marginally better prompt escapes. But maybe I'm holding it wrong. But zsh is at least 3X more complex than bash, and bash already has way more features than a sane shell would.

    So I've been reading an awful lot of zsh documentation.

    #ComputersSuck

  14. MacOS' default shell is zsh. I don't know why. The only advantage I've found is that it has marginally better prompt escapes. But maybe I'm holding it wrong. But zsh is at least 3X more complex than bash, and bash already has way more features than a sane shell would.

    So I've been reading an awful lot of zsh documentation.

    #ComputersSuck

  15. I have a bunch of scripts. Some of them are under Home Manager, but most of them are just sitting in ~/bin because the version control and world-building steps slow down development.

    Some of them intentionally conflict with MacOS' programs. For example: I overrode mdfind, MacOS' CLI interface to Spotlight search.

    #ComputersSuck

  16. I have a bunch of scripts. Some of them are under Home Manager, but most of them are just sitting in ~/bin because the version control and world-building steps slow down development.

    Some of them intentionally conflict with MacOS' programs. For example: I overrode mdfind, MacOS' CLI interface to Spotlight search.

    #ComputersSuck

  17. PlatformIO, bless their heart, have given all their commands unique names, so it doesn't matter where they are in the path. Except for python* and pip*, but you don't have to run those directly. Shell wrappers invoke PlatformIO's Python in a standard (I think?) venv.

    ESP-IDF runs whatever python is at the front of the path, then complains that it's not the one it wanted.

    #ComputersSuck

  18. PlatformIO, bless their heart, have given all their commands unique names, so it doesn't matter where they are in the path. Except for python* and pip*, but you don't have to run those directly. Shell wrappers invoke PlatformIO's Python in a standard (I think?) venv.

    ESP-IDF runs whatever python is at the front of the path, then complains that it's not the one it wanted.

    #ComputersSuck

  19. Apple has a program called path_helper that reorders PATH. It calls it from /etc/zprofile, which is on the readonly / filesystem. It puts Apple's directories ahead of my directories. Apple's Unix userland is pathetic.

    Home Manager and nix make a twisty maze of little scripts, I can't keep track of them all, which put their stuff in front. It's good stuff -- I selected it -- but some of it needs to be overridden.

    #ComputersSuck

  20. Apple has a program called path_helper that reorders PATH. It calls it from /etc/zprofile, which is on the readonly / filesystem. It puts Apple's directories ahead of my directories. Apple's Unix userland is pathetic.

    Home Manager and nix make a twisty maze of little scripts, I can't keep track of them all, which put their stuff in front. It's good stuff -- I selected it -- but some of it needs to be overridden.

    #ComputersSuck

  21. The basic problem is that several different organizations are fighting in the dotfiles over the order of my search path.

    Apple says it knows best, reorders PATH to put all its 15-year-old userland stuff in front.
    Home Manager says it knows best, puts its stuff in front.
    PlatformIO just wants its stuff in there somewhere.
    I say I'm in charge -- I own the Mac -- but my stuff is at the end.

    #ComputersSuck

  22. The basic problem is that several different organizations are fighting in the dotfiles over the order of my search path.

    Apple says it knows best, reorders PATH to put all its 15-year-old userland stuff in front.
    Home Manager says it knows best, puts its stuff in front.
    PlatformIO just wants its stuff in there somewhere.
    I say I'm in charge -- I own the Mac -- but my stuff is at the end.

    #ComputersSuck

  23. This week in computers suck: I tried to install ESP-IDF, got lost in a twisty maze of environment variables and failed to install it for two whole days, and I might finally have figured out why my Mac's command search path has been AFU since I installed home-manager last year.

    A hopefully short thread.

    #ComputersSuck #HomeManager #MacOS

  24. This week in computers suck: I tried to install ESP-IDF, got lost in a twisty maze of environment variables and failed to install it for two whole days, and I might finally have figured out why my Mac's command search path has been AFU since I installed home-manager last year.

    A hopefully short thread.

    #ComputersSuck #HomeManager #MacOS

  25. 2.5 hours of hot-aisle data-center action and my head hurts and i want to go back to bed again.
    #computersSuck #HotAislesBlow

  26. Clang having a hissy fit because we accidentally included a GCC header is just such a fun thing to fuck around with on a Friday afternoon...

    #computersSuck #compilersSuck #headerFilesSuck #dockerSucks #crossCompilingSucks

  27. Clang having a hissy fit because we accidentally included a GCC header is just such a fun thing to fuck around with on a Friday afternoon...

    #computersSuck #compilersSuck #headerFilesSuck #dockerSucks #crossCompilingSucks

  28. Current technology irritations:

    1) I am getting repeat notifications on my Mac, and I can't figure it out how to fix it in the allotted ~2 minutes I have a patience for.

    2) I can't get any languages servers working in my IDE, so I'm working with just syntax highlighting. This is probably MacOS's fault, but who knows, and I can't figure it out in the ~1 hour I have patience for.

    #ComputersSuck

  29. Current technology irritations:

    1) I am getting repeat notifications on my Mac, and I can't figure it out how to fix it in the allotted ~2 minutes I have a patience for.

    2) I can't get any languages servers working in my IDE, so I'm working with just syntax highlighting. This is probably MacOS's fault, but who knows, and I can't figure it out in the ~1 hour I have patience for.

    #ComputersSuck

  30. Why is highlighting text on computing devices so janky? Dragging over text highlights almost completely unpredictably. Words, lines, paragraphs, *previous* paragraphs (WTF?), flicker back and forth as you drag out your selection.

    Or is that just me?

    #ComputersSuck

  31. Why is highlighting text on computing devices so janky? Dragging over text highlights almost completely unpredictably. Words, lines, paragraphs, *previous* paragraphs (WTF?), flicker back and forth as you drag out your selection.

    Or is that just me?

    #ComputersSuck

  32. Why on earth is this computer not seeing the bootable usb with YUNoHost on it. Top of boot priorities in bios, ports are all on in bios, tried all the ports, I even tried formatting it to FAT32 before putting the files on it… 😩

    #halp #computersSuck