VIM - Vi Improved

hello :))

I hope this post is okay. I just wanted to share, that I've created a new community on lemmy for talking about the modal text-editor Kakoune (inspired by vim).

It is located at [email protected] and you're welcome to join whether you're using kakoune already or just want to learn about it :))

by @[email protected]

cross-posted from: https://derp.foo/post/233472

There is a discussion on Hacker News, but feel free to comment here as well.

Looks like the project is in good hands and will make gentle steps forward.

cross-posted from: https://lemmy.world/post/2712042

Bram Moolenaar, the creator of the widely respected Vim code editor, has passed away at the age of 62. The family announced his passing in a heartfelt Google Groups message on August 5, revealing a sudden progression of a medical condition that had afflicted him.

Hi, I am new to Lemmy Is it possible that I am the 2nd subscriber to this channel(or however it is called in the Lemmyverse) ?

Seen a few ways but all seem to be with deprecated/abandoned methods or tools

Solution:

1. Make all command substition in a make done through the assignment operator e.g.

cflags != pkg-config --cflags gtk4
libs != pkg-config --libs gtk4

all:
	gcc $(cflags) -o watch main.c $(libs)

not

all:
	gcc $$(pkg-config --cflags gtk4) -o watch main.c $$(pkg-config --libs gtk4)

2. add this to your .vimrc: let g:ale_c_parse_makefile = 1

ALE gives me a warning when I use gtk

#include <gtk/gtk.h> /* E: gtk/gtk.h: No such file or directory

This is probably happening because ALE isn't using my compiler flags gcc $( pkg-config --cflags gtk4 ) -o program main.c $( pkg-config --libs gtk4 ) that I stole from the gtk documentation. These compiler flags allow gcc to find gtk/gtk.h even though it is in gtk-4.0/gtk/gtk.h

How do I make ALE aware of my compiler flags?

Hi, I have set up my neovim config listchars like so:

vim.opt.listchars = { tab = "│ ", trail = "·", precedes = "<", extends = ">", nbsp = "○" }

But for empty lines between the indentations there are these awful holes left.

I used to use intent-blankline.nvim but I want to try to tone down my plugin usage, and I pretty much used it only to fix this issue, could somebody help me?

A guy at my work had this printed out and hanging in his office.

I switched over to the completion plugin that is part of https://github.com/echasnovski/mini.nvim and I'm impressed with how suitable it is for my use case without any configuration

Sure, it's not as extensible, but it's so set-and-forget and still gives suggestions from LSP

There is a project to modernize the bundled color schemes in vim.

SpaceVim is a distribution of the Vim editor that’s inspired by spacemacs. It manages collections of plugins in layers, which help collecting related packages together to provide features. This approach helps keeping configuration organized and reduces overhead for the user by keeping them from having to think about what packages to install.

The three last articles are mandatories

This plugin adds Go language support for Vim. It includes:

• Commands for building, installling, running, testing, etc.
• Improved syntax highlighting and folding.
• Goto symbol declaration and documentation lookup.
• Debugging, completion, formatting, linting, etc. with gopls.

BSD 3-Clause License

vim-plug, written by Junegunn, is one of the most popular Vim plugin managers out there.

• Easy to set up: Single file. No boilerplate code required.
• Easy to use: Concise, intuitive syntax
• Super-fast parallel installation/update (with any of +job, +python, +python3, +ruby, or Neovim)
• Creates shallow clones to minimize disk space usage and download time
• On-demand loading for faster startup time
• Can review and rollback updates
• Branch/tag/commit support
• Post-update hooks
• Support for externally managed plugins

MIT License

Junegunn writes about vim-plug in his blog post Writing my own Vim plugin manager.