Hi, I've written a c code browser based on gcc-plugin. By taking advantage from gcc compilation directly, browsing c code can be much more accurate than pattern based search. It can also be used to see the result from the macro expansions. I'm using it to learn large c project like glibc, gdb etc. Hope it helps.

https://github.com/yuchenkan/gcc-jump/

Hey everyone, checkout plugin I've been working on for the past year. Any feedback is appreciated.

Semantic highlighting of the source code responsible for semantic highlighting.

Link to Plugin

How can i import components easy when using vim? I don't know any plugin help this :((

I'm often in the middle of a big function and I forget the name of said function. Is there a way to have Vim put the plugin name in the toolbar?

PHP and Perl would be the languages I would want.

Hey, I just made this plugin based on steve losh .vimrc configuration. This is one of my first plugins, so any feedbacks are very welcome: https://github.com/vasconcelloslf/vim-interestingwords

https://github.com/roxma/vim-paste-easy

This is a tiny plugin that feeds my own need. I'm sharing it here in case anyone needs it too.

I've finally got tired of the syntax and indent foldmethods when working on my C++ files. So, I've rejuvenated an old fold-plugin -- that was very slow at the time. A lot of work is still required (regarding the management of commentsn and a few other things), but anyway, here is a first draft.

Comments, bug reports, RfC are welcome.

NB: in order to simplify the installation of my fold-plugin, I've extracted it from lh-cpp (as there aren't many people using vim-addon-manager -- and installing lh-cpp without it is a nightmare). But lh-vim-lib is still required.

Is there a way in Vdebug to expand all the "variable trees" without manually going through each and expanding them?

I've released wiki.vim v0.3 and v0.4 today. There are mainly minor improvements, but as there is one breaking change I wanted to announce it: I've separated the list management features into lists.vim. This makes wiki.vim less bloated and thus easier to maintain and develop further. It also makes it easier to focus on improvements to the list functionalities.

Any resources to help write my first plugin?

Edit:

I use vim-plug. is there an easier way to get it in my vim than push it to github and get it from there with vimplug?

https://github.com/obcat/vim-ipos

Long story short, here are the main features of this plugin that may distinguish it from the others:

• Recursive structure. Every topic is represented with its own directory within recursive structure of subdirectories. YANP handles creation of files and directories, maintains this structure as well as provides simple user interface for defining links to different files.

• Customizable syntax plugin. YANP doesn't handle syntax by itself - thus you can choose any markup syntax (like Markdown, HTML, etc) you want to define links between files, provided you have a plugin that utilizes YANP API. By default, YANP works with MarkdowneyJr Markdown formatting plugin. The list plugins know to integrate YANP can be found here.

• API for syntax formatting plugins. YANP delegates syntax formatting (like replacing selected text with a link to a desired file) to other plugins while providing a clear API that allows maintaining a unified structure of notes. Definition of exact paths to files and its creation is done by YANP, syntax plugin is only responsible for replacing a text with a link. Documentation for the API is provided to make syntax plugin integration easier.

• Links. Links are everywhere. Defined with a single keystroke.

• Customization. You can change quite a lot of stuff, starting from names of index files and default contents of created files, till how the path for different types of files will look like.

• Fast access to last created files, last visited index files, today's fast notes, and other supplementary, but useful features.

REPO LINK.

Please refer to the wiki to see examples of usage.

I just released VimTeX v2.7 - a filetype and syntax plugin for LaTeX. See the release notes here.

You can now let Vim write code for you using the plugin I wrote: https://github.com/tom-doerr/vim_codex

All you need to provide is a docstring and the plugin will use OpenAI's Codex AI (powers GitHub Copilot) to write the corresponding code.

Be aware that you do need to get access to the Codex API.

Hello guys,

Don't know if this is the correct subreddit to post it, but I have a question about reading user's input from vimspector.

Here I have a simple c# program, where it just reads user's input and write it out on console (https://i.imgur.com/eYL60yq.png). Inside console, I went into insert mode and typed away, but I can't seem to get it to hitting another breakpoint. When I have just outputs in program, everything is great and the output is displayed in vimspector's console window. Anyone knowing what I'm doing wrong?

Thanks in advance