We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
org_mappings.meta_return doesnt skip past the contents of the heading
* Heading | <- Put cursor here Line 1 Line 2
Heading content should be skipped past
Behaves as expected in Emacs
local tmp_dir = vim.env.TMPDIR or vim.env.TMP or vim.env.TEMP or '/tmp' local nvim_root = tmp_dir .. '/nvim_orgmode' local lazy_root = nvim_root .. '/lazy' local lazypath = lazy_root .. '/lazy.nvim' -- Install lazy.nvim if not already installed if not vim.loop.fs_stat(lazypath) then vim.fn.system({ 'git', 'clone', '--filter=blob:none', 'https://github.com/folke/lazy.nvim.git' }) end vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { 'nvim-orgmode/orgmode', event = 'VeryLazy', ft = { 'org' }, config = function() require('orgmode').setup() end, }, }, { root = lazy_root, lockfile = nvim_root .. '/lazy.json', install = { missing = false, }, }) require('lazy').sync({ wait = true, show = false, }) vim.keymap.set('i', '<C-CR>', function () require"orgmode".action("org_mappings.meta_return") end, { buffer = true })
In nvim-orgmode:
In Emacs:
Windows 10
NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713484068
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
org_mappings.meta_return doesnt skip past the contents of the heading
Steps to reproduce
Expected behavior
Heading content should be skipped past
Emacs functionality
Behaves as expected in Emacs
Minimal init.lua
Screenshots and recordings
In nvim-orgmode:
In Emacs:
OS / Distro
Windows 10
Neovim version/commit
NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713484068
Additional context
No response
The text was updated successfully, but these errors were encountered: