search

nvim-lua / plenary.nvim

plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
MIT License
2.62k stars 280 forks source link

How to see full error messages (without elision)? #428

Open masaeedu opened 1 year ago

masaeedu commented 1 year ago

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.

mert-microsoft commented 6 months ago

+1 to this. It is really hard to debug errors without seeing full trace