![]() TLDR is that with the global lvim object, custom path, breakages because of unstable plugins it causes a lot of support issues where people go to the official NeoVim channel and not the LunarVim one. The other alternative they suggested was One of the things I noticed about LunarVim is that they were not very receptive about it in the official NeoVim rooms whereas people there (including NeoVim developers) were quite positive about LazyVim. When it gets right down to it, there are only a couple little tweaks from my old setup I want to carry over, everything else I want to go back to using defaults (places where I've diverged my own functionality) and stop pushing around a poorly maintained manual config that gives me 10% of what Lunar or similar gives. But, the capabilities of having Language Server in vim have been so refreshing! Particularly when working with Python 2 code to bring it up to Python 3, pretty much just follow what Language Server says. LunarVIM has been a bit tricky, mostly related to upgrades around LunarVIM, usually neovim updates. ![]() I program maybe 5% of the time, so the stuff I do to make it IDE-like often isn't worth maintaining for that 5% time, so I often end up with partially working plugins or whatnot. Partly because of the 100s of machines issue, partly because of managing plugins and interactions between them. A year or so ago I threw away all my custom vimrc and went with (nearly) bone stock LunarVim, and have really enjoyed getting off the treadmill of maintaining a custom vim setup. Sysadm here as well, been using vi since the '80s. ![]() I choose the latter because i spend SO much time staring at my editor and trying to convince it to do things that are almost always better with automated assistance from it. ![]() You _can_ accept pre-made defaults like those provided by VSCode OR you can gradually refine your editor to be a perfectly crafted tool for your particular and very individual way of thinking. The less configurable an editor is the less it will be able to support the way your brain likes to work. The fact is that _your_ brain is different from everyone else's. VERY rarely, you'll want to tweak it in a way that there isn't a plugin / config for and you'll find communities of very helpful people who'll respond with "what about this solution." With ALL editors you eventually encounter "ugh, this is frustrating" or "i wish i didn't have to do that" and then you have 30+ years of plugins and configs you can draw on to modify it to match your liking without any coding. that's not how it works unless that's what your brain wants. I 100% agree with your hyperbolic "200 keybinds to make a view component" But that's. BUT, what they both offer better than anything else, is the ability to gradually modify them to match what your brain needs. In the given table, each row has an assigned row height.The thing about vim and emacs is that both of them, out of the box, suck. If we run the above code, it will display a window with a table and some data in it. The rowheight property will add internal padding to each row in the table. To set the row height of the Treeview widget, you can create an instance of ttk themed widget where you can specify the rowheight property. We can also configure the properties of the treeview widget such as its color, size, column width, height, row width & height, etc. The table can have rows and columns in which we can insert the data instantly. With the Treeview widget, we can insert our data in the form of a table. The treeview widget in Tkinter provides a way to represent the data in a hierarchical structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |