smart_action not mapped to <CR>

[marchyman]

This may be more of an nvim question than an obsidian.nvim question. Anyway, after the latest update is no longer following links. <cmd>Obsidian follow_links<cr> works fine; it looks like was never mapped to smart_action in the buffers keymap. WhichKey confirms that there is no mapping for . Inspecting vim.bo in a markdown file also shows the buffer keymap is empty.

Any hints on how I might track down why this is happening?

[neo451]

try running nvim --clean -u minimal.lua in the install directory of this plugin. to debug this in a clean environment.
I refactored this recently, but I don't see why it is missing.

[marchyman]

I changed to ~/.local/share/nvim/lazy/obsidian.nvim and ran the above command. The resulting checkhealt had all OK.
I q the checkhealth and entered :e /path/to/a/file/in/my/vault

Return in normal mode moves the cursor to the next line.
:= vim.inspect(vim.bo.keymap) returns '""'.
:Obsidian follow_link when on a link works.

Does that help? FWIW I'm running an nvim I built from source yesterday. However, I earlier tried the release version of nvim and got the same results. I also tried adding a callback section to my config. The keymap I added there was not in the buffer, either.

[neo451]

1. see :h 'keymap' keymap is not a list of keymaps, so it is rightfully empty.
2. I tested on two machines in empty environments, it all worked fine.
3. for now you can try:

vim.api.nvim_create_autocmd("User", {
  pattern = "ObsidianNoteEnter",
  callback = function(ev)
    vim.keymap.set("n", "<CR>", require"obsidian.builtin".smart_action, {
      buffer = ev.buf,
      expr = true,
      desc = "Obsidian Smart Action",
    })
  end,
})

or like the callback style in https://github.com/obsidian-nvim/obsidian.nvim/wiki/Keymaps

[neo451]

I think it should be resolved by cc80395

[marchyman]

Thanks for the note on keymap... you may be able to tell I'm a neovim novice and still have a lot to learn. That said...

Neither of the above helped. But in more playing I see that the location of my vault -- in iCloud accessed via a symbolic link in my mac documents folder -- has something to do with it. I opened a different vault that lives on my local disk and it works as expected.

I'll play some to see if I can figure out what is going on because I'm curious and might learn something.

Thanks again.

[neo451]

yes someone discovered the symlink issue as well, I have an rough idea where the issue is and should be able to fix it tomorrow, but feel free to poke around the code!

#240 (comment)

[neo451]

@marchyman d30a98a tell me if this fix it.

[marchyman]

Yup. Working just fine. Many thanks.