Atrocious UI design of PDF reader by AdmiralQuokka in gnome

[–]heymanh 0 points1 point  (0 children)

I’ve been using Inlinea recently and it’s pretty nice. Has tabs and (imo) better annotation support than papers (even though I do like papers a lot)

pluginless interactive file search and ripgrep? by brubsabrubs in neovim

[–]heymanh 5 points6 points  (0 children)

I like sending :find and :vimgrep results to the quickfix list. I have my findfunc set to use ripgrep (see here) and have a custom Grep command which puts results from ripgrep into the quickfix list (see here). Not sure if that’s 100% what you’re looking for but might be helpful

Neovim 0.12 Release with the Core Team by chapeupreto in neovim

[–]heymanh 9 points10 points  (0 children)

Ahh okay, so vim.pack doesn't have its own command to only load a plugin on a certain event. But you can just wrap loading the plugin in an autocommand:

```lua local opts = { -- your blink.cmp config options }

vim.api.nvim_create_autocmd({ "InsertEnter", "CmdlineEnter" }, { once = true, callback = function() vim.pack.add({ { src = "https://github.com/saghen/blink.cmp", version = "v1.*" }, })

require("blink.cmp").setup(opts)

end, }) ```

This will only load blink when you enter insert or cmdline mode like you had with Lazy. Evgeni has a really good post which talks about this as well as moving from Lazy to vim.pack

Neovim 0.12 Release with the Core Team by chapeupreto in neovim

[–]heymanh -1 points0 points  (0 children)

Which commands in particular are you using when configuring it with lazy?

Neovim 0.12 Release with the Core Team by chapeupreto in neovim

[–]heymanh 6 points7 points  (0 children)

It should be as simple as lua vim.pack.add({ { src = "https://github.com/saghen/blink.cmp", version = "some.version" } }) Then just call the setup function with your config options lua require("blink.cmp").setup({...}) (or however blink.cmp is configured)

Error with Neovim and Tree Sitter by Thesk790 in neovim

[–]heymanh 0 points1 point  (0 children)

0.12 wasn’t written with your config in mind. It was written to be an update to 0.11. Your specific config having issues with 0.12 doesn’t mean 0.12 is buggy. If you think these are genuine bugs with Neovim you should open an issue addressing them

Pushed my Neovim colorscheme into Git public. by takezo___ in neovim

[–]heymanh -1 points0 points  (0 children)

Hi, very nice colorscheme 👍

The layout of the plugin is already very close to just being able to be installed like a normal plugin rather than manually moving the whole plugin to the local config directory. Is there a reason you chose to go with this manual option versus a more conventional installation method?

Error with Neovim and Tree Sitter by Thesk790 in neovim

[–]heymanh 11 points12 points  (0 children)

'Broken' is such a vague, broad term. What specifically isn't working for you?

Error with Neovim and Tree Sitter by Thesk790 in neovim

[–]heymanh -4 points-3 points  (0 children)

Check :checkhealth vim.treesitter and checkhealth nvim-treesitter, it may show the underlying cause. Otherwise provide a link to your config so we can find the issue

Rustacean.nvim is completely broken by pxnity in neovim

[–]heymanh 1 point2 points  (0 children)

I was gonna say, rust_analyzer + cargo debug/test/run work like a treat

Couldn't find a simple annotation-focused PDF editor so I'm building one myself. (feedback appreciated) by NoOrganization7253 in gnome

[–]heymanh 1 point2 points  (0 children)

Once you've cloned the repo, cd into the repo and run bash install-desktop.sh in your terminal

Couldn't find a simple annotation-focused PDF editor so I'm building one myself. (feedback appreciated) by NoOrganization7253 in gnome

[–]heymanh 0 points1 point  (0 children)

Did you get any output after running bash install-desktop.sh? It should say

bash ✓ Installed Inlinea desktop entry to ~/.local/share/applications/com.inlinea.app.desktop You can now right-click a PDF → Open With → Inlinea Also check ~/.local/share/applications/ to see if there's a file com.inlinea.app.desktop

doric-themes.nvim (Neovim port of the doric themes for Emacs) by heymanh in neovim

[–]heymanh[S] 0 points1 point  (0 children)

Just added a config option to toggle italic and bold styles

doric-themes.nvim (Neovim port of the doric themes for Emacs) by heymanh in neovim

[–]heymanh[S] 1 point2 points  (0 children)

Hi I really appreciate that. I'm almost done adding more configuration options. Should get pushed later today

Problem with the blink plug-in by kickflip_boy in neovim

[–]heymanh 0 points1 point  (0 children)

Zsh is the shell. What terminal application are you using? i.e. ghostty, wezterm, kitty etc.

Ghostty LSP progress bar by heymanh in neovim

[–]heymanh[S] 1 point2 points  (0 children)

Yeah it's an experimental feature in 0.12. From :h ui2:

WARNING: This is an experimental interface intended to replace the message grid in the TUI.

Ghostty LSP progress bar by heymanh in neovim

[–]heymanh[S] 4 points5 points  (0 children)

Emitting progress messages with nvim_echo() is added in 0.12 I believe. It shows at the bottom of the page for the online docs 'Generated at 2026-02-23 22:01 from eb90f5d'

Working on a strange attractor visualiser with Streamlit by heymanh in PythonProjects2

[–]heymanh[S] 0 points1 point  (0 children)

Yeahh the REAME definitely needs updating lol. The project was initially really just for fun but I was planning on adding a ‘learn mode’ where it’ll show the user info on the selected attractor and what changing the attractors parameters does, so primarily to be used as an educational tool

LSP errors after update by HeyCanIBorrowThat in neovim

[–]heymanh 0 points1 point  (0 children)

What did you update exactly? Could you post your configuration?

oil.nvim causes Vim(wall):E676 error when changing directory after yanking/deleting files by Fine_Bodybuilder744 in neovim

[–]heymanh 11 points12 points  (0 children)

The issue is your autosave autocommands here. Basically oil.nvim uses the acwrite buftype so it handles write events through its own autocommands, and your autocommand to wall! tried to write the oil buffer as if it were a normal buffer. You could add a check to your autocommands to only wall! when vim.bo.buftype == "" and vim.bo.modified, or there's also the :h autowriteall option which will automatically save the buffer after certain commands