r/neovim

Or do you have some other, better approach?

As a fresher in India, I kept missing job openings at product companies like Razorpay, CRED, Groww, and PhonePe. By the time I saw them on LinkedIn, hundreds had already applied.

So I built HiringRadar — a Telegram bot that scrapes these companies' career pages directly and sends alerts the moment a new position is posted. No middleman, no delay.

It's live and working. Currently tracks Razorpay, PhonePe, Groww, and CRED. More companies coming soon.

Would love feedback from fellow freshers and anyone who's been through the Indian job hunt. What companies should I add next?

In this video, I customize the Neovim statusline from scratch without using any plugins.

We start with the statusline option and learn how to add different items to it, use colors and highlight groups, and create functions to provide dynamic information.

Then I show how to display the current mode, use external tools to provide information, and add useful Git and LSP information to the statusline.

Topics covered:

• The statusline option
• Adding items to the statusline
• Colors and highlight groups
• Functions in the statusline
• Showing the current mode
• Using external tools
• Git information
• LSP information

Everything is built using Neovim's built-in functionality, without relying on a statusline plugin.

Video: https://youtu.be/7nslXbSH12E

Source Code: https://github.com/FractalCodeRicardo/dev-config/blob/master/nvim/lua/my/status-line-example.lua

Is it just me, or does nvim-surround not work with multicursor? I do Q on multiple lines, and v$S) only surrounds the line of the cursor.

A while ago lervag pointed out (#34) that my markdown-preview.nvim has the same name as iamcco's much older markdown-preview.nvim. With both installed, lazy.nvim treats them as one plugin, and iamcco's buffer-local commands hide mine in markdown buffers. I said I'd rename it, so here it is, together with the server plugin it runs on, whose name was shared with other plugins too:

• markdown-preview.nvim is now mdkite.nvim: https://github.com/selimacerbas/mdkite.nvim
• live-server.nvim is now kitehost.nvim: https://github.com/selimacerbas/kitehost.nvim

Nothing breaks if you leave your config alone for now. GitHub redirects the old repo URLs, and the old require and commands keep working through 2.x. They print a deprecation warning once per session and go away in 3.0.

To switch, update the spec:

{
  "selimacerbas/mdkite.nvim",
  dependencies = { "selimacerbas/kitehost.nvim" },
  opts = {},
}

require("markdown_preview") becomes require("mdkite"), and the commands are now one :MdKite with subcommands (:MdKite, :MdKite stop, :MdKite refresh, :MdKite toggle). kitehost works the same way: :KiteHost start, :KiteHost status, :KiteHost stop. After updating, :Lazy clean removes the old copies.

If you haven't used them: mdkite renders the whole buffer in your browser and updates as you type over Server-Sent Events, with scroll sync. Mermaid diagrams come out as SVGs you can zoom, pan and export, and math goes through KaTeX. It's Lua plus a page in your browser, so there's nothing to npm install.

kitehost is the piece some of you might want on its own. It's a small local web server for Neovim, written in pure Lua on vim.uv, with no Node or Python behind it. Run :KiteHost start on a file or folder (with Telescope installed you get a picker for the path and port), and the browser reloads every time you save. A stylesheet change is swapped in place without a full reload, and a folder with no index.html gets a directory listing. Starting again on the same port points the running server at the new path, so your open tab keeps working. It can also start on its own when you open an HTML file, and it can show running servers in your statusline. It binds to 127.0.0.1 by default; if you open it to your network, set a token. Other plugins can use it as a library too, which is how mdkite runs on top of it.

Other changes in 2.0:

• kitehost 2.0 is also a security release. It checks the Host header, so a DNS rebinding page can't read your local server, and it closes a few ways around the token on protected paths. The details are in the advisories on the repo, plus one on mdkite for an old CORS issue that was fixed in 1.10. mdkite 2.0 requires kitehost 2.0.
• kitehost now needs Neovim 0.10 or newer, like mdkite. On 0.8 or 0.9, pin kitehost v1.5.0, which keeps the old names. CI runs both on Linux, macOS and Windows.
• mdkite 2.1 previews dotted filetypes that have a markdown part (like rzk.markdown) and adds a filetypes option for things like quarto. Thanks to ddxtanx for the PR.

Coming up: separate previews per buffer (#33) and an offline mode for the browser assets. Bug reports and ideas are welcome on either repo, and thanks again to lervag for raising the name clash.

The new paragraph leads with what people would use kitehost for, a live-reloading local server for plain HTML and CSS work. The library angle comes last, since that matters mostly to plugin authors.

Its perfect for me, that doesn't mean it will be perfect for you..

Try it out. Give me feedbacks. I would like to improve this more..

Or if you have issues. Please let me know.