nvim-orgmode / nvim-orgmode/orgmode

opt: expected table, got string

Open
#1,036 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Lua
Stars
3.9k
Forks
190
Avg merge
2d 13h
Merged PRs (30d)
7

Description

Describe the bug

I used the config from README.md (https://github.com/nvim-orgmode/orgmode/blob/a49d5d4c479cbf70acf261c1e8f1f69947ed1b81/README.org#installation)

and got the error:

Failed to run `config` for orgmode

...a/lazy/orgmode/lua/orgmode/config/mappings/map_entry.lua:53: opt: expected table, got string
# stacktrace:
- vim\shared.lua:936 _in_ **validate**
- orgmode\lua\orgmode\config\mappings\map_entry.lua:53 _in_ **action**
- orgmode\lua\orgmode\config\mappings\init.lua:5
- orgmode\lua\orgmode\config\init.lua:6
- orgmode\lua\orgmode\init.lua:122 _in_ **setup**
- AppData/Local/nvim/lua/plugins/lazy.lua:10 _in_ **config**
- scoop/apps/neovim/current/share/nvim/runtime/filetype.lua:36
- scoop/apps/neovim/current/share/nvim/runtime/filetype.lua:35
                                                                                          
checkhealth

orgmode: require("orgmode.health").check()

Orgmode ~

  • ERROR Treesitter grammar is not installed. Run :Org install_treesitter_grammar to install it.
  • ERROR Failed to run healthcheck for "orgmode" plugin. Exception:
    ...Data/Local/nvim-data/lazy/orgmode/lua/orgmode/health.lua:55: loop or previous error loading module 'orgmode.config'
Steps to reproduce

Use the default config from README.md and open an .org file.

Expected behavior

orgmode starts without error.

Emacs functionality

No response

Minimal init.lua

-- Enter your minimal_init.lua here

Screenshots and recordings

No response

nvim-orgmode version

a49d5d4

OS / Distro

Windows 10

Neovim version/commit

NVIM v0.10.3 Build type: Release LuaJIT 2.1.1713484068 Run "nvim -V1 -v" for more info

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the installation configuration in README.org and the validation failure at lua/orgmode/config/mappings/map_entry.lua:53. Reproduce it by opening an .org file with the documented configuration, then trace the reported mapping option and verify that Orgmode starts without the “expected table, got string” error.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, vim
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.