How to see full error messages (without elision)?

Open
#428 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with lua/plenary/async/async.lua at the reported lines 18, 45, 48, and 108, then trace how the coroutine error is formatted. Check whether the ellipses are introduced there and whether an existing option controls them; done means identifying the source and documenting or exposing the relevant behavior.

Written by the indexing model from the issue text.

Description

Hello there. I'm not sure if this is the right place to post this, please feel free to close if not.

I'm trying to debug an error message I'm seeing with a plugin that uses plenary. The error message looks like this:

Error detected while processing BufWritePost Autocommands for "*":
Error executing lua callback: ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...te/pack/packer/start/neotest/lua/neotest/client/init.lua:358: neotest-haskell:/home/masaeedu/code/awake
/end-to-end/parse-graph/src/haskell/eaql/code
stack traceback:
        [C]: in function 'error'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:108: in function 'run'
        ...te/pack/packer/start/neotest/lua/neotest/client/init.lua:354: in function <...te/pack/packer/start/neotest/lua/neotest/client/init.lua:352>

I am wondering if all those ellipses (in the file paths, and also after The coroutine failed with this message: ...te/) are introduced by plenary itself, and whether this feature can somehow be turned off globally so that I can see the full output.

Thanks.

Dominant language
Lua
Stars
3.5k
Forks
340
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.