lldb.nvim
lldb.nvim copied to clipboard
dbgx
Complain about unsaved session file after `:LLsession show`?
After running :LLsession new, there is no lldb-nvim.json file to be found in the current folder, nor in my whole home directory. Running :LLsession show shows me a buffer with the expected content, which hasn’t be written to disk yet. If I save it manually, it will save the session to disk.
I thought it could be due to having set hidden in my config file, but removing it did not help. AFAIR, I already had the same issue when I tried lldb.nvim a year ago.
lldb.nvim: HEAD at 222c7706be4a47fe0a6105b8d1c728812bad538e Neovim: 0.1.6 Python2: 2.7.12 python2-neovim-client: 0.1.10 Neovim config file: https://gist.github.com/pierremoreau/1fa99bdda563f7e4e6753e9dbae06613 (Distribution: Arch Linux)
Sorry for the late response...
That is the expected behavior. This is to delegate file management to the user (e.g. handling an existing config file).
On Oct 31, 2016 15:17, "Pierre Moreau" [email protected] wrote:
After running :LLsession new, there is no lldb-nvim.json file to be found in the current folder, nor in my whole home directory. Running :LLsession show shows me a buffer with the expected content, which hasn’t be written to disk yet. If I save it manually, it will save the session to disk.
I thought it could be due to having set hidden in my config file, but removing it did not help. AFAIR, I already had the same issue when I tried lldb.nvim a year ago.
lldb.nvim: HEAD at 222c770 https://github.com/critiqjo/lldb.nvim/commit/222c7706be4a47fe0a6105b8d1c728812bad538e Neovim: 0.1.6 Python2: 2.7.12 python2-neovim-client: 0.1.10 Neovim config file: https://gist.github.com/pierremoreau/ 1fa99bdda563f7e4e6753e9dbae06613 (Distribution: Arch Linux)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/critiqjo/lldb.nvim/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/ABXrGbCiafpXVSOS4qj4XjR1qt_Pre-8ks5q5bk0gaJpZM4Kk1Un .
Ah, ok. To me, the "write session file to" message meant that it was going to write that file to disk, not just create a buffer with the appropriate content. I am not sure why, when I close nvim, I do not get a message about unsaved modifications for the buffer created by lldb.nvim, but I do get it for the buffers I created manually. That would have made it clearer from the beginning that I needed to manually save that buffer. :-)
There could maybe be some notes in the documentation about the fact that you need to save manually. On the other hand, it doesn’t look like other people complain about it, so might be obvious to others.
Hmm... I don't think it's that obvious. And I'm not quite sure how to make it complain either. I'll look into it when I get time. So I'll leave this open for now...