increase/decrease date seem to have the wrong key maps

[pillmuncher]

Describe the bug

The README and orgmode.txt both say that increasing a date can be done with <C-a> and decreasing with <C-x>. I find that this is not so on my installation where those key maps seem to work on the year, but work backwards when the cursor is over the month or the day, that is <C-a> decreases and <C-x> increases month and day, respectively.

:verbose nmap <C-a> in an org buffer gives me:

n  <C-A>       *@<Cmd>lua require("orgmode").action("org_mappings.timestamp_up")<CR>
                 org increase timestamp
	Last set from ~/.local/share/nvim/lazy/orgmode/ftplugin/org.lua

I get the same when I ask for <C-A>, and similar for <C-x> and <C-X>.

Any of these :verbose nmap commands in non-org buffers gives me No mapping found.

checkhealth

==============================================================================
orgmode: ✅

Orgmode ~

• ✅ OK Treesitter grammar installed (version 2.0.0)
• ✅ OK Setup called
• ✅ OK org_agenda_files configured
• ✅ OK org_default_notes_file configured

Steps to reproduce

1. put cursor over year of date
2. press <C-a>
3. watch the year increase
4. put cursor over month or day of date
5. press <C-a>
6. watch the month/day decrease

The same for <C-x> in the other direction.

Expected behavior

pressing <C-a> or <C-x> over any part of a date should always have the same behavior, not a behavior opposite to what the docs say for the month and day parts.

Emacs functionality

No response

Minimal init.lua

~/.config/nvim/lua/plugins/nvimorgmode.lua:

return {
	"nvim-orgmode/orgmode",
	event = "VeryLazy",
	ft = { "org" },
	config = function()
		-- Setup orgmode
		require("orgmode").setup({
			org_agenda_files = "~/orgfiles/**/*",
			org_default_notes_file = "~/orgfiles/refile.org",
		})
	end,
}

Package manager is lazy.nvim.

~/.config/nvim/init.lua:

...
local lazypath = vim.fn.stdpath("data") .. "/lazy/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",
		"--branch=stable", -- latest stable release
		lazypath,
	})
end
vim.opt.rtp:prepend(lazypath)

-- load the plugins:
require("lazy").setup("plugins")
...

I have not changed the mappings for <C-a>, <C-A>, <C-x>, or <C-X>.

The complete list of my plugins:

    ● aerial.nvim 0.71ms  start
    ● barbecue 5.06ms  start
    ● cmp-nvim-lsp 0.06ms 󰢱 cmp_nvim_lsp  nvim-lspconfig
    ● cmp_luasnip 0.26ms  nvim-cmp
    ● Comment.nvim 1.57ms  start
    ● conform.nvim 0.57ms  start
    ● fidget.nvim 0.04ms  nvim-lspconfig
    ● friendly-snippets 0.07ms  nvim-cmp
    ● git-worktree.nvim 0.09ms  start
    ● gitsigns.nvim 1.7ms 󰢱 gitsigns  settings.mappings
    ● indent-blankline.nvim 2.07ms  start
    ● lazy.nvim 5.22ms  init.lua
    ● lazydev.nvim 2ms  nvim-lspconfig
    ● lazygit.nvim 0.21ms  start
    ● lualine.nvim 9.72ms  start
    ● luarocks.nvim 10.84ms  start
    ● LuaSnip 5.12ms  nvim-cmp
    ● mason-lspconfig.nvim 2.92ms  nvim-lspconfig
    ● mason.nvim 2.62ms  mason-lspconfig.nvim
    ● mellifluous.nvim 0.56ms  start
    ● mini.icons 0.16ms  which-key.nvim
    ● mini.nvim 0.2ms  which-key.nvim
    ● neotest 16.1ms  start
    ● neotest-bash 0.26ms  neotest
    ● neotest-dotnet 0.27ms  neotest
    ● neotest-plenary 0.25ms  neotest
    ● neotest-python 0.31ms  neotest
    ● neotest-vim-test 0.25ms  neotest
    ● nvim-cmp 21.68ms  start
    ● nvim-coverage 3.7ms  start
    ● nvim-lspconfig 26.31ms  start
    ● nvim-navic 0.13ms  barbecue
    ● nvim-nio 0.25ms  neotest
    ● nvim-tree.lua 13.16ms  start
    ● nvim-treesitter 7.26ms  refactoring.nvim
    ● nvim-treesitter-textobjects 5.71ms  nvim-treesitter
    ● nvim-web-devicons 0.17ms  lualine.nvim
    ● orgmode 3.52ms  VeryLazy
    ● playground 0.51ms  nvim-treesitter
    ● plenary.nvim 0.2ms  nvim-coverage
    ● rainbow-delimiters.nvim 1ms  lua
    ● refactoring.nvim 17.55ms  start
    ● telescope-fzf-native.nvim 0.3ms  telescope.nvim
    ● telescope.nvim 7.5ms 󰢱 telescope  settings.mappings
    ● transparent.nvim 1.44ms  start
    ● undotree 0.39ms  start
    ● vim-obsession 0.33ms  start
    ● which-key.nvim 0.93ms  nvim-lspconfig

  Not Loaded (2)
    ○ luvit-meta 
    ○ nvim-autopairs  InsertEnter 

Screenshots and recordings

No response

nvim-orgmode version

git says a5f0a0a, :Lazy says f4dde88

OS / Distro

Solus Linux Budgie 10.9.2

Neovim version/commit

NVIM v0.11.4 Build type: RelWithDebInfo LuaJIT 2.1.1744014795

Additional context

No response

[kristijanhusak]

Can you give me an example org file with the date that you are attempting to increase/decrease? Also, the minimal init you provided is not a minimal init provided in the repo. Did you confirm it's not working without any other plugins?

[pillmuncher]

I saved the minimal init from the repo as ~/tmp/mininal.lua.
I created a minimal org file ~/tmp/minimal.org.
I opened it in ~/tmp with nvim -u mininal.lua minimal.org

This is what minimal.org contains:

* 2025-9-8

The behavior is still the same.
Cursor over the year: <C-a> increases, <C-x> decreases.
Cursor over the month or day: <C-a> decreases, <C-x> increases.

HTH.

[kristijanhusak]

That is not a valid orgmode date. Date needs to be enclosed either in <> to be treated as "active" date, or enclosed in [] to be treated as inactive date. Example: <2025-09-12> or [2025-09-12]

[pillmuncher]

Using any of the date formats below results in the same behavior I described earlier:

2025-9-8
<2025-9-8>
[2025-9-8]
* 2025-9-8
* <2025-9-8>
* [2025-9-8]

[kristijanhusak]

Those are not valid date formats according to orgmode specification. It needs to be YYYY-MM-DD . See more here https://orgmode.org/manual/Timestamps.html