…from people who seem to refuse to install paredit or coloring plugins for either? ps lisp syntax ftw, it’s a feature!

  • Barbarian@sh.itjust.works
    link
    fedilink
    arrow-up
    33
    ·
    5 months ago

    As long as the next line also has 5 spaces, that’s fine. Python only complains about inconsistency, not the exact number of spaces/tabs.

      • smeg@feddit.uk
        link
        fedilink
        English
        arrow-up
        4
        ·
        5 months ago

        What, you don’t like tabs and spaces being syntactically different?

        • Buddahriffic@lemmy.world
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          5 months ago

          (Sarcasm/deadpan detected but I’ll respond anyways).

          Not when they are visibly the same and the spaces have no other meaning in that context.

          Not to mention tabs being annoying in general because of how badly it works to adjust the distance of tab stops. That doesn’t really affect this particular case, but it’s why I generally use spaces instead of tabs.

          Most of the annoyance is from vim recognizing that spaces are an error in makefile recipes but still using them unless I copy paste a tab in, including when I hit enter on a line that is using a tab already. It matches the indentation but uses spaces instead of tabs. I’m sure there’s a way to adjust vim config to fix this, but I have yet to acquire the esoteric knowledge required to do so.

          • ugo@feddit.it
            link
            fedilink
            arrow-up
            2
            ·
            5 months ago

            If by vim you mean neovim

            vim.api.nvim_create_autocmd(“fileType”, {
                group = file_type_group,
                pattern = “make”,
                command = “setlocal ts=4 sts=4 sw=4 noexpandtab”,
            })
            

            Slap this in your config, done