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

Question: why does constrain_cursor not work? #533

Open
3 tasks done
ValynTyler opened this issue Dec 9, 2024 · 1 comment
Open
3 tasks done

Question: why does constrain_cursor not work? #533

ValynTyler opened this issue Dec 9, 2024 · 1 comment
Labels
bug Something isn't working question Further information is requested

Comments

@ValynTyler
Copy link

Did you check the docs and existing issues?

  • I have read the docs
  • I have searched the existing issues

Neovim version (nvim -v)

0.8.0

Operating system/version

NixOS

Describe the bug

Screencast From 2024-12-09 01-38-40.webm
Going up and down a line with j and k results in cursor escaping the editable text area. This happens nomatter what constrain_cursor is set to. Please help

What is the severity of this bug?

minor (annoyance)

Steps To Reproduce

open neovim and go down a line, where the file or directory name is shorter than the one of the current line.

Expected Behavior

I would expect it not to do this.

Directory structure

No response

Repro

-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "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",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

  • I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.
@ValynTyler ValynTyler added the bug Something isn't working label Dec 9, 2024
@stevearc
Copy link
Owner

Can you confirm that this happens with the minimal repro config? It does not look like you used it in your screencast.

@stevearc stevearc added the question Further information is requested label Dec 10, 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 question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants