• 28 Posts
  • 367 Comments
Joined 11 months ago
cake
Cake day: July 23rd, 2023

help-circle




  • Well I’ve only given Neovim a spin for a few hours, but it’s been nothing but an exercise in frustration. Yeah syntax off works in vanilla nvim, but it’s replaced by treesitter commands if treesitter is enabled. And treesitter is really, really invasive and aggressive when it comes to highlighting and transparently rewriting what’s on the screen.

    So basically, without treesitter, it’s like vim, only more annoying to configure because init.lua is wildly inconsistent. With treesitter, it breaks my workflow at best (but I suppose I could get used to it) and it silently modifies what I see on the screen vs what I’m actually editing at worst, which is a hard no-no for me.

    I think maybe if I configured treesitter from the ground up, I could manage to make it leave my text alone, keep the regex-based syntax highlighting which suits me just fine, and only make treesitter suggest things - which is the only feature I wanted to try Neovim for really. But it’s just not worth the incredimazing complication. I’ve survived just fine without smart hinting from vi for decades, so I can easily do without it.

    But hey, thanks man 🙂


  • Okay so…

    I reinstalled Neovim 11 from scratch. ~/.config/nvim/ is empty:

    • I start “nvim Makefile”, type “test:<ENTER”: Neovim inserts a tab.
    • I start “nvim Makefile”, type “:se noautoindent” (or “:se noai”) then “test:<ENTER>”: Neovim inserts a tab - i.e. Neovim ignores noautoindent
    • I start “nvim Makefile”, type “:se indentexpr=” then “test:<ENTER>”: Neovim does NOT insert a tab: that works!
    • I put “se indentexpr=” in ~/.config/nvim/init.vim, start “nvim Makefile”, type “test:<ENTER”: Neovim inserts a tab - i.e. it ignores the statement in init.vim. But it doesn’t ignore other statements in init.vim: if I put “se bg=light” in it for instance, the background does indeed show up as light.

    So it seems the crux of the issue is that init.vim isn’t parsed properly.

    EDIT: but putting “filetype indent off” in ~/config/nvim/init.vim seems to do the trick. Thanks for the hint! This is a lot more complicated than it needs to be 🙂

    EDIT #2: “:syntax off” doesn’t turn off the syntax either. Well, I’ve had enough. Back to plain old vim…



  • I tried issuing the commands inside Neovim itself, just in case it was a configuration loading issue. They don’t do anything. It’s maddening.

    If you want to reproduce it, open a Makefile type a target, ENTER, and no matter what any autoindent setting is set to, the next line is indented by one tab, as if writing the recipe for that target. Nothing I do by hand, inside Neovim, after it’s loaded and ready to use, will change that.



  • I’m not using anything at the moment.

    My intention was to give naked Neovim a spin and make sure it performs how I like Vim to perform. Then once it covers what I consider the basics, I was planning on layering kickstart.nvim on top of it and customizing Kickstart to my odd tastes.

    The problem being, my odd tastes include:

    1/ ABSOLUTELY NO AUTOINDENT. I hate autoindent with a burning passion, in all circumstances

    2/ Must work in an 80-column terminal, meaning no line numbers - or at least line numbers that can be disabled. I’ve survived 40 years without line numbers, I can go on without them a few more 🙂

    Right now I’m stuck at 1/ without even having installed Kickstart. I’m not installing it until I manage to disable autoindent. And I still haven’t found out how to do that, so I’m back to vanilla Vim for now because I have work to do.








  • That’s a far better option for the environment. I can’t speak on the privacy aspect since who knows what your bus system does.

    Yes that’s true, especially since half of our city’s fleet is now electric.

    The bus is great and I usually like it, especially since I don’t like driving so much. But here’s the thing: I’m getting older, and it’s getting more and more tiring to change buses and wait outside in the dead of winter when it’s zero degrees out, and doing a 50-minute commute that only takes 20 minutes by car. I’m all for the environment, but my creaky gen-X frame is starting to complain about my lifestyle. I’m not lazy and I try my best, but I just don’t have the stamina anymore.

    In the winter, I find myself using my old diesel more and more out of sheer tiredness, and I’d rather not: that thing is all shades of terrible environmentally in the cold and it’s not good for the engine anyway. And now with my employer essentially offering free electricity, it’s really tempting to buy an EV, at least for the winter months.







  • open source wasn’t really a thing in the 90s and early 2000s

    Truly written as someone who wasn’t alive back then and just makes stuff up.

    Open-source - which was called free software back then - was very much alive and totally a thing since forever, and especially in the 70s, 80s and 90s. I learned all I know with free software in the 80s. Linux came out in 91 and was a pure product of open source: Minix - the forerunner of Linux - was a fully open-source OS created in 87, and GNU had been around since 83.

    Please read up on things you don’t know before posting nonsense.