Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Mapping a function, concatenates the compile commandd with the result. #546

Open
3 tasks done
druidamix opened this issue Nov 24, 2023 · 1 comment
Open
3 tasks done
Labels
bug Something isn't working stale

Comments

@druidamix
Copy link

Did you check docs and existing issues?

  • I have read all the which-key.nvim docs
  • I have searched the existing issues of which-key.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.9.4 Build type: Release

Operating system/version

archlinux

Describe the bug

Hello,
Mapping a function on a key has a problem.

For example ExecRun() function mapped on r in a test program results on:

23 42 179un' '/home/druida/Projects/xgo/main.go' 2>&1| tee /tmp/nvim.druida/icK2o
Account balance 159

while running the command GoRun directly:

:!'go' 'run' '/home/druida/Projects/xgo/main.go' 2>&1| tee /tmp/nvim.druida/icK2o
2/3
23 42 179
Account balance 159

-- copied whichkey example
function ExecRun()
if vim.bo.filetype == "rust" then
vim.cmd("RustRun")
elseif vim.bo.filetype == "go" then
vim.cmd("GoRun")
end
end

local mappings = {
-- ["e"] = { "NvimTreeToggle", "Explorer" },
["e"] = { "Neotree", "Explorer" },

c = {
name = "Code",
r = { ExecRun, "ExecRun" },
g = { "GoRun", "GoRun" },
p = { "RustRun", "RustRun" },
b = { "GoBuild", "GoBuild" },
l = { "Golint", "GoLint" }

},

Steps To Reproduce

  1. Create a function like:
    function ExecRun() if vim.bo.filetype == "rust" then vim.cmd("RustRun") elseif vim.bo.filetype == "go" then vim.cmd("GoRun") end end
  2. Map the function on a key.
  3. Run the key to see the result of a simple program like rust or go to se mixed result.

Expected Behavior

It is expected see console result below the compiler run command.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "folke/which-key.nvim", config = true },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here
@druidamix druidamix added the bug Something isn't working label Nov 24, 2023
Copy link
Contributor

github-actions bot commented Jul 6, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant