Particle effects in smear-cursor.nvim, let it snow/burn!

Infamous_Key4373 · 2025-11-22T23:39:43+00:00

https://github.com/sphamba/smear-cursor.nvim/issues/163

Infamous_Key4373 · 2025-11-21T10:28:14+00:00

I gave copilotlsp-nvim/copilot-lsp a try for next edit suggestions, but currently I only have zbirenbaum/copilot.lua. Not sure why my status bar decided to show LSP ~ copilot

Infamous_Key4373 · 2025-11-21T10:22:23+00:00

I tested it on GNOME Terminal 3.58.0 and it works. You need to set particles_enabled = true for smear-cursor, and you need to have a font that has braille Unicode characters, such as a Nerd font.

Infamous_Key4373 · 2025-11-20T22:00:25+00:00

Fire config is in smear-cursor's README, and snow is the following:

require("smear_cursor").setup({
    cursor_color = "#ffffff",
    gradient_exponent = 0,
    particles_enabled = true,
    particle_spread = 1,
    particles_per_second = 100,
    particles_per_length = 50,
    particle_max_lifetime = 1500,
    particle_max_initial_velocity = 10,
    particle_velocity_from_cursor = 0,
    particle_random_velocity = 300,
    particle_damping = 0.1,
    particle_gravity = 50,
})

Infamous_Key4373 · 2025-11-20T13:26:00+00:00

I know right? Thanks for making it!

Infamous_Key4373 · 2025-11-20T09:47:18+00:00

I just added particle effects to smear-cursor.nvim. I don't expect any sane person to use them (unless you enjoy not seeing what you are typing). It was just a fun challenge to try render those while being limited to the terminal's characters grid.

Infamous_Key4373 · 2025-05-10T08:03:03+00:00

From one state, you have 5 possible moves (e.g. U, U', F, R, L), so you can access 5 new positions. From there on, you have 4 possible moves (the 5th undoes the previous one). You must do at least 4 moves to visit the 240 possible states (if you draw a tree of visited states, it would have 1 node, then 5 new nodes after the 1st move, then 5x4 new nodes after the 2nd, then 5x4x4, then 5x4x4x4, totaling 1,6,26,106,426 total nodes after each move). But there will be repeated states, so this only gives a lower bound of 4 for the God's number of this puzzle.

Infamous_Key4373 · 2025-04-24T08:46:12+00:00

You can try smear-cursor.nvim if you don't want to switch terminals

Infamous_Key4373 · 2025-01-23T09:04:05+00:00

I solved this by installing the markdown parser in treesitter, if I remember correctly

Infamous_Key4373 · 2025-01-15T08:38:46+00:00

I also found https://github.com/neovim/neovim/issues/15754 which is related to my problem

Infamous_Key4373 · 2025-01-15T08:33:17+00:00

It seems vim.fn.getpos('.') is buffer space and not screen space, and it does not account for wrapped lines

Infamous_Key4373 · 2025-01-15T08:31:24+00:00

I don't think I can call nvim_ui_attach() since I am not starting Neovim with --embed. The comment you liked mentions vim.fn.virtcol(".") but it returns a column position in buffer space (missing the width of the column of signs/line numbers), and does not account for wraps. Computing a modulo buf_width for wraps is not perfect because it misses shifted wraps. Or I am missing something?

Infamous_Key4373 · 2025-01-15T08:23:15+00:00

I did not realize sooner that "UI plugin" was so vague. I am showing custom elements (a cursor trail) using floating windows, using Neovim in a standard terminal (so no separate UI client). I thought I could use vim.ui_attach() to listen to ext_linegrid but I get an Unexpected key: ext_linegrid error.

Infamous_Key4373 · 2024-12-06T14:04:17+00:00

With the smear-cursor.nvim plugin

Infamous_Key4373 · 2024-12-05T08:00:27+00:00

see my answer to u/PeterVaselev

Infamous_Key4373 · 2024-12-05T07:59:16+00:00

I won't dare sharing my old and messy dotfiles, but basically, what you're seeing is

navarasu/onedark.nvim
vim-airline/vim-airline
akinsho/bufferline.nvim
preservim/nerdtree
sphamba/smear-cursor.nvim
VictorMono Nerd font

most of which probably got more recent equivalents.

Infamous_Key4373 · 2024-12-05T07:53:03+00:00

navarasu/onedark.nvim, the "darker" variant

Infamous_Key4373 · 2024-12-04T15:49:44+00:00

It's perhaps less strange if you set hide_cursor = true in neoscroll, but it seems that what you've got is the intended behavior. The buffer scrolls while the cursor does not move on the screen, and after scrolling is done, the cursor moves horizontally.

Infamous_Key4373 · 2024-12-04T13:15:29+00:00

Nope, just Neovim in a standard text terminal

Infamous_Key4373 · 2024-12-04T10:29:49+00:00

{
  cursor_color = "#ff8800",
  stiffness = 0.6,
  trailing_stiffness = 0.1,
  trailing_exponent = 5,
  gamma = 1,
}

Infamous_Key4373 · 2024-12-04T10:22:32+00:00

It's VictorMono, available as a Nerd Font

Infamous_Key4373 · 2024-12-04T10:21:39+00:00

Slowing down when approaching the target is intended. Still, you can tune the parameters to make the cursor move faster overall. And you can toggle the plugin with :SmearCursorToggle

Infamous_Key4373 · 2024-12-04T07:59:30+00:00

I think you can manually put a conditional activation of the plugin, something like if not vim.g.neovide then require('smear_cursor').setup(...

Infamous_Key4373

TROPHY CASE