• cybersandwich@lemmy.world
      7·
      1 year ago

      I always thought vim should have a message that shows in the command area “To quit type :q or :wq” or something like that.

      That message shows until you update your config to not show it. If you are updating a vim config, you are past the point of needing that message.

      • papertowels@lemmy.one
        4·
        1 year ago

        I was picking up obsidian as a note taking app - in order to turn on vim mode it had you type in the command to quit vim. Every vim integration needs that.

  • lukini@beehaw.org
    91·
    1 year ago

    Glamorize an overworked, mentally unwell character? This isn’t the show you wanna use for this cause…

  • tacosanonymous@lemm.ee
    72·
    1 year ago

    I’m not sure I support getting wasted and fucking a penguin.

    You do you, for sure, but I’m not going to sign off on it.

  • hitagi@ani.social
    4·
    1 year ago

    I was surprised to see the local feed flooded earlier. The bot must have bugged out or something. I don’t know if I should purge those posts or just let it be.

    • chaorace@lemmy.sdf.orgEnglish
      2·
      1 year ago

      There was a YouPoll outage that clogged up the bot, so a couple days worth of episode discussion posts got posted all at once. That alone wasn’t too bad, but… then I decided to load up the Fall 2023 episode config while I was at it and fat-fingered in the Winter 2023 episode config instead (AKA: the already finished season from 9 months ago). I’m ashamed to say that this led to posting hundreds of pointless threads from one of the most boring seasons in recent memory – an embarassing and strictly human error on my part.

      Unfortunately these posts can’t really be effectively deleted because the pre-existing holo code which Shinobu uses as a base will just go and regenerate the missing threads. This regenerating issue could have been avoided had I taken an SQLite database backup beforehand… but as evidenced by the posts still being up I clearly failed to do that.

      Moving forward, my plan is to A) aggressively take database backups when loading seasonal episode configs in the future & B) conduct a pre-load sanity check on the contents of each seasonal episode config file prior to importing it as an added precaution against misreading filenames.