[BUG] Every first screenshot fails with "node code selected"

[willdavidow]

Just installed the plugin and everything works fine for the most part, but it seems the first attempt always fails when trying to generate screenshots to both the clipboard or the save path.

Steps to reproduce

Open nvim and any file Select code and attempt to generate screenshot

Result

no code is selected

Expected

Screenshot generated to either clipboard or save path

When I de-select and re-select the exact code, in the exact same way, everything works fine.. it's just that first attempt that doesn't work.

https://github.com/mistricky/codesnap.nvim/assets/763985/8ec61a14-5231-47e9-b388-a414ba599033

[mistricky]

Hi @willdavidow, thx for this issue reporting, that's interesting bug but I can't reproduce on my machine.

but it seems the first attempt always fails when trying to generate screenshots to both the clipboard or the save path.

The "first attempt" refer to the first screenshot taken after first CodeSnap was installed or the first screenshot taken after opening nvim every time?

[willdavidow]

The "first attempt" refer to the first screenshot taken after first CodeSnap was installed or the first screenshot taken after opening nvim every time?

It's every time after closing and reopening nvim.

[mistricky]

What version of your Neovim? If you enter command instead of use hotkey, did it works?

[DrummyFloyd]

i have the same behaviour upon the couple of first time , when i opend nvim ( LAZYVIM config here)

with command line it work like a charm

return {
  {
    "mistricky/codesnap.nvim",
    build = "make build_generator",
    keys = {
      { "<leader>cs", "<cmd>CodeSnap<cr>", mode = "x", desc = "Save selected code snapshot into clipboard" },
      { "<leader>cS", "<cmd>CodeSnapSave<cr>", mode = "x", desc = "Save selected code snapshot in ~/Pictures/" },
    },
    lazy = true, <= same behaviour with true or false
    opts = {
      mac_window_bar = false,
      save_path = "~/Pictures/",
      has_breadcrumbs = true,
      bg_theme = "sea",
      watermark = "",
      code_font_family = "FiraCode Nerd Font",
      has_line_number = true,
      show_workspace = false,
    },
  },
}

could be related to Lazy event ??

EDIT: i tried on both stable 9.5 adn nightly for Neovim

[willdavidow]

What version of your Neovim? If you enter command instead of use hotkey, did it works?

I'm running nvim nightly: NVIM v0.10.0-dev-3094+ge14e75099-Homebrew - updated a day or two ago.

Running the command directly does work just fine.

[HugoxSaraiva]

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details.

To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>.

As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

[DrummyFloyd]

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details.

To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>.

As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

Work as expected, but for me it's kinda of a Workaround , if i check with many other keymap there is no <Esc>

[marcinjahn]

I guess the issue I'm having is related.

My config (LazyVim):

return {
  "mistricky/codesnap.nvim",
  build = "make",
  opts = {
    has_breadcrumbs = true,
    has_line_number = true,
    bg_color = "#212121",
    bg_padding = 0,
    watermark = "",
    mac_window_bar = false,
  },
  keys = {
    { "<leader>cp", "<cmd>CodeSnap<cr>", mode = "x", desc = "Snap selected code into clipboard" },
    { "<leader>cP", "<cmd>CodeSnapHighlight<cr>", mode = "x", desc = "Snap and highlight code into clipboard" },
  },
}

When I select some class manually (SHIFT-V and jjj), and use the keymap (<leader>cp), I get proper result:

However, when I select that class using vac keys (it uses treesitter to highlight "outside the class"), the keymap (<leader>cp) results in:

Basically, it snaps just the line where my cursor was when I executed vac.

The same scenario works totally fine when invoking the :CodeSnap command

[HugoxSaraiva]

Hi @marcinjahn,

Have you tried the workaround I've described? This seems like the lag by one I mentioned. I guess the scenario works when invoking the :CodeSnap command because you have to enter command mode to invoke it. The selection used on :CodeSnap is updated when you exit visual mode to enter command mode, but that does not occur when you use <leader>cp without the <Esc> workaround.

[Rallanvila]

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details.

To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>.

As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details.

To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>.

As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details.

To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>.

As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

My codesnap.lua file

return {
  "mistricky/codesnap.nvim",
  build = "make build_generator",
  keys = {
    { "<leader>cc", "<Esc><cmd>CodeSnap<cr>", mode = "x", desc = "Save selected code snapshot into clipboard" },
    { "<leader>cs", "<cmd>CodeSnapSave<cr>", mode = "x", desc = "Save selected code snapshot in ~/Pictures" },
  },
  opts = {
    save_path = "~/Pictures",
    has_breadcrumbs = true,
    show_workspace = true,
    has_line_numbers = true,
    bg_theme = "bamboo",
  },
}

I tried this fix however I continue to get No executable codelens found at current line when I highlight the code and <leader>cc

[DrummyFloyd]

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details. To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>. As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details. To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>. As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

I encountered the same issue, but it appears I've found a solution. It seems that the markers '< and >' retain values from the previous visual mode selection. When Neovim is opened, they are set to 0. You can read this for more details. To resolve this, I simply adjusted my configuration to exit visual mode before calling CodeSnap. Executing the following command: <Esc><cmd>CodeSnap<cr>. As this bug arises due to the plugin attempting to retrieve the last selection markers rather than the current selection, it could imply that the snapshot result consistently lags by one. However, that requires further verification.

My codesnap.lua file

return {
  "mistricky/codesnap.nvim",
  build = "make build_generator",
  keys = {
    { "<leader>cc", "<Esc><cmd>CodeSnap<cr>", mode = "x", desc = "Save selected code snapshot into clipboard" },
    { "<leader>cs", "<cmd>CodeSnapSave<cr>", mode = "x", desc = "Save selected code snapshot in ~/Pictures" },
  },
  opts = {
    save_path = "~/Pictures",
    has_breadcrumbs = true,
    show_workspace = true,
    has_line_numbers = true,
    bg_theme = "bamboo",
  },
}

I tried this fix however I continue to get No executable codelens found at current line when I highlight the code and <leader>cc

it's because u did not override the keymaps from lazyVim, your issue is not related to CodeSnap but with your keysmaps

[Rallanvila]

I don't understand. I have nothing bound to <leader>cc in my keymaps and it's bound to run codelens

I copied the install instructions, which enabled these configs, as I don't have anything else configured to use those bindings.

[willdavidow]

I don't understand. I have nothing bound to <leader>cc in my keymaps and it's bound to run codelens

I copied the install instructions, which enabled these configs, as I don't have anything else configured to use those bindings.

start neovim with nvim -V1 and then run verbose vmap <leader>cc to see where that keybinding is set in your config

[Rallanvila]

@willdavidow

So it looks like it's mapped correctly, however, when I try to use it, I get No executable codelens found at current line

[willdavidow]

@Rallanvila you might need to set it for x mode.

if it helps at all, here's my config:

return {
  "mistricky/codesnap.nvim",
  build = "make build_generator",
  -- opts = {
  -- },
  config = function()
    require("codesnap").setup {
      save_path = "~/Desktop",
      file_extension = "png",
      has_breadcrumbs = true,
      has_line_number = true,
      watermark = "",
      bg_color = "#535c68",
      bg_padding = 0,
      code_font_family = "JetBrainsMonoNL Nerd Font",
      watermark_font_family = "JetBrainsMonoNL Nerd Font",
      -- prefix = "📸 ",
      -- default options
      -- prefix = "📸 ",
      -- prompt = "Enter a name for the snapshot: ",
      -- file_path = "~/Desktop/",
      -- file_name = nil,
      -- file_extension = "png",
      -- highlight = "Visual",
      -- highlight_group = "Visual",
      -- highlight_file = nil,
      -- highlight_format = "png",
      -- highlight_options = {},
      -- silent = false,
      -- callback = nil,
    }
    local wk = require "which-key"
    wk.add {
      { "<leader>cc", "<cmd>CodeSnap<cr>", desc = "Save selected code snapshot into clipboard", mode = { "v", "x" } },
      { "<leader>cs", "<cmd>CodeSnapSave<cr>", desc = "Save selected code snapshot to ~/Desktop", mode = { "v", "x" } },
    }
  end,
}

[Rallanvila]

@willdavidow, thanks for the config, I don't know what's going on. I c/p'd it in and you can see the commented code above from what I tried to run previously as well.

[willdavidow]

@Rallanvila It looks like the key bindings here are not overriding the code lens setting. I don't use LazyVim, just the Lazy package installer - so I'm not sure if there's a special way to override keybindings.

It looks to me like the lazily loaded language server key bindings for whatever file you're in are getting set after this plugin so you'd need a way to override that, or an easier approach would be to just pick an unused key binding/combination.

[Rallanvila]

I mapped it to something else and it worked. I couldn't figure out how to override the mappings for my life. I appreciate you @willdavidow 🙏🏼