To understand terminal capitalism, first you must understand recursion.

  • Ansis100@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    6 hours ago

    Ignoring the AI going haywire for a bit - what is that feature request? I seriously can’t wrap my head around it. What even is the point it’s trying to make?

    • T156@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      58 minutes ago

      From what I can tell, they want the program to close when you write exit instead of /exit. Guessing it currently does the latter, and does a “did you mean /exit” sort of thing.

      • lambalicious@lemmy.sdf.orgOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        45 minutes ago

        I understood it as enabling exit in addition to /exit. It’s honestly a reasonable request unless “exit” is already an internal keyword. I assume the presence of “/exit” in the text also somehow affects an effect on the Microslop bot misbehaving.

        • T156@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          27 minutes ago

          I don’t think it was. It was them putting the triage tag on themselves that seems to have put it into a loop, at least going by the progression of events.

          The user put on the tag, the bot removes the tag, because only maintainers can put that on, and then puts on the tag, after which it removes it because someone who wasn’t a maintainer put the tag on.


          I could see exit being an issue if you’re doing something in the CLI that might cause you to type that without passing it as a command (“What do you want the program to do after the task is complete?” “Exit”), but I’m not familiar enough with the program to say one way or the other.