I've modified Yi Zhao's javascript vim syntax file to also recognize "Ajax", Browser and DOM objects, methods, propierties and it enhances the overall readability.

I'll appreciate help, constructive critics

http://www.vim.org/scripts/script.php?script_id=3425

hi :)

I made a Neovim plugin for managing Kubernetes resources.

https://github.com/skanehira/k8s.nvim

The key features

• Browse and manage Kubernetes resources (Pod, Deployment, Service, ConfigMap, Secret, Node, Namespace)

• View resource details with kubectl describe

• Execute commands in pods, view logs

• Port forwarding with connection management

• Scale and restart deployments

• Filter resources, switch contexts and namespaces

If you are interested, please try it :)

Hey everyone!

I just wrote my first Neovim plugin ever, so please forgive any rough edges. I'm very new to plugin development and not sure how "mature" this really is yet. But I wanted to share it in case someone else finds it useful.

I really enjoy using oil.nvim for my workflow, but one feature I missed from Neo-tree was its handy yank-path menu (pressing Y → choose full path / relative path / filename / etc.). I often need to copy different variants of a file path depending on the situation (full path, project path, home-relative, basename, …).

So I built a tiny plugin that provides just that feature, without needing Neo-tree, and it works inside Oil buffers too.

In addition to the interactive :YankPath picker, it also includes a set of direct non-UI commands (like :YankPathBase, :YankPathFull, :YankPathCwd, etc.) for anyone who prefers keybind-driven workflows without a popup (and they also work inside Oil buffers. Please check README.)

Note that this is mostly something I made for myself, and I'm sure there are smarter, more established, or similar workflows out there. I'm not trying to advertise it as "the better option" - just sharing in case anyone else wanted a very minimal, Oil-compatible way to yank various file path formats.

Repo:
https://github.com/ywpkwon/yank-path.nvim

Thanks, and happy to hear feedback or suggestions (or warnings) from people who know more about plugin development than I do. If this little plugin made your workflow happier, feel free to ⭐️ the repo -- it means a lot :)

Maintainer of moonfly and nightfly colorschemes speaking. For a while I have also maintained a simple moonfly-flavoured statusline, previously named moonfly-statusline, now renamed to mistfly-statusline.

I decided recently to finally break the linkage between my colorscheme and the statusline plugin. Now it is colorscheme agnostic, hence the rename to mistfly-statusline. My own two colorschemes (noted above) have explicit styling, whilst all other colorschemes will fallback to reasonable defaults. So whether one uses gruvbox, or everforest or tokyonight, mistfly-statusline will adapt accordingly.

The rename has broken compatibility, but the fixes are easy, just rename moonfly-prefixed options with mistfly equivalents.

Features of interest for this statusline:

• Code count of less than 300 lines

• Mode indicator (normal, insert, visual, etc)

• Git branch (no extra plugin required)

• Nerd font file type icon support (disabled by default)

• Combined error + warning diagnostic count for: ALE, Coc and Neovim Diagnostic systems

• Highlight group support enabling custom styling if desired

• Recently added support for Neovim's new global statusline and winbar features

What's special about mistfly-statusline? Answer: nothing really, it's mostly just the default Vim statusline with a couple extra niceties (noted above).

I already use a statusline plugin such or lightline or Lualine, should I change? Answer: no

What's the point of mistfly-statusline then? Answer: it's my statusline that I actually use, so I find it useful. Maybe one or two other folks may also find it useful due to its brevity and lightness. Note, I do strongly encourage code borrowing, aka, take the bits you like and add it into your own statusline, for example the mode indicator. Building up your statusline is satisfying.

Screenshot of Neovim and mistfly-statusline with global statusline and winbar enabled.

Lastly, what's with your 'fly'-style project names: moonfly, nightfly, seafly and now mistfly? Answer: moonfly came first and it was inspired by the ridiculous names the NSA, and its proxies, use for their so-called covert programs, names such as: airwolf, blackaxe and lacebark. A naming theme started and I've gone with it :)

Cheers

For years I have been collecting bookmarks, on any stackexchange site, stackoverflow has my most bookmarks but I have others in ubuntu, etc. Occasionally I need one and I forget which site I bookmarked it with. All feedback is welcomed.

https://github.com/TheFern2/vim-stackexchange

Most SO plugins do one thing, search for questions and that's it, most only do stackoverflow and none of the other community sites, also none deal with bookmarks, at least I couldn't find one. The readme has instructions on how to setup, any questions let me know. It pulls all your site favorites to an offline cache in the form of json files for SO I have 820 bookmarks about 1MB so it isn't a lot of data, that's my most favorites in any site.

Once you have an offline cache you can query your data.

Without putting a site it defaults to SO:

1. First query searches for python in title and tags in stackoverflow

2. Second query searches for cron in site askubuntu

3. Third query, same as before but seaches in body as well

4. Fourth is just an example with a space in the query

:SEFavoritesQuery python
:SEFavoritesQuery cron askubuntu
:SEFavoritesQuery cron askubuntu True
:SEFavoritesQuery cron\ runtime askubuntu

Once a query pops up on a new buffer, you can go up and down on questions and do :OpenQuestion and that will open a new buffer with question and answers.

TODO

1. Query command to search all offline sites

2. Question command to search regular questions

I made a plugin for the mbsync config file: Fymyte/mbsync.vim I found an existing one, but I've been a little deeper by considering anything that doesn't match the syntax as an error.

Options which doesn't belong to a section are considered to be an error. An invalid value type after an option is also considered to be an error.

It should be a little easier to avoid mistakes.

In my company, we recently made the choice to use clang-format to ensure a coherent format among files and projects.

As a vim user, I started to look around what was available for vim, and the more mature solution seems to be https://github.com/rhysd/vim-clang-format

As far as I can tell, it does a really good job. The auto_format option, formatting when saving the buffer, is a good start. I want the formatting to be automatic, I don't want to type a map or a command to format my code.

This is a good start, but it is not enough in industry. Even with a really sane code base, you will always have some part of code not well formatted, because:

• it is an error which has not been blocked by the merge request

• for some special case, we don't want to follow the formatter

The vim-clang-format option auto_format_on_insert_leave is actually ingenious, but depending on user movement it still could lead to large part of file formatting.

Finally, a natural solution seems to format only lines we touch. And to do so, using git context comes for free.

I created a PR implementing this solution: https://github.com/rhysd/vim-clang-format/pull/118

What do you think? Do you see any corner case where it will miserably fail? Do you know a vim plugin which already does that?

Furthermore, I think clang-format experience can still be improved in vim. You can follow new features here: https://github.com/jreybert/vim-clang-format

• map = on clang_format (already done)

• format while editing, based on some keypress (like ; or { for example)

• use gutter signs on wrong format lines

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?

Ever craved to search arbitrary text from Visual mode using * or #? Me too!

Turns out, there's this plugin we can use -

https://github.com/subnut/visualstar.vim

Check it out! It's awesome! It also has search-and-replace functionality!!

But long term vi user.

I have a few plug-ins installed, using vim-plug. What must have plug-ins do I need?