-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changing dap-mode locals cap #667
Comments
We have discord here: https://discord.com/invite/swuxy5AAgT Can you check if dap-ui-variable-length works for you. |
Thanks for reminding me about that. I did discover that I had already set it at 10000 my configuration. I can confirm that is what it currently is set at with describe-variable. It doesn't appear to have any effect. Running the latest Ubuntu install of Emacs 27.1 |
Can you do: |
I wish I could, but the data is sensitive information. My message buffer is getting cropped, too. I set the eval-expression-print-length to nil, but I'm only getting a portion of the readout. Is there something specific you are looking for in the message buffer that I can look for? |
You mean that the message does not have the whole data? I want to find out who is cutting the data, the UI or the server. Also you can still create a function foo with one param "bar" with long value and send me the data for that fuction (it won't have antyhing sensitive) |
There is |
Ok, I found the issue. I will try to provide a fix tomorrow my time. |
Now you can use something like |
JFYI don't upgrade treemacs when upgrading dap-mode because latest version of lsp-mode won't work with latest treemacs |
Which version does it work with, so I know what to roll back to? |
@bridgesense Alexander-Miller/treemacs#677 (comment) |
Sorry to be a bother. When using the use-package command with lsp-mode, do the requirements override quelpa statements in the emacs config? I uninstalled treemacs completely with the package manager and package-autoremove. I placed this in my emacs config, prior to lsp stuff:
But latest treemacs files still keep getting pulled? |
I am not use-package expert, but putting something like this just before the use-package declaration should work:
|
Also make sure that it runs before any package that requires |
Yeah, I tried compiling that version of treemacs and swapping out the files and lsp-treemacs wouldn't run. Perhaps I need an older package of that, too? dap-mode pretty much runs out of the box for a clean emacs install. This last commit breaks it. I'm sure there is a way to get this to work, but until there is some documentation to support installation workarounds -- I'd roll this back. EDIT: I tried rolling dap-mode back to yesterday's commit. The local variables don't even show up. I wish I had backed things up! :( |
After tearing out and reinstalling everything, it's just the local variables that no longer show up. This may be an unrelated issue to another update that happened, because even when I roll back -- it's the local variables that are missing. |
Is this what you were talking about, as far as the Treemacs issue? I rolled EVERYTHING back to a couple of months ago. I compiled all the LSP modules from at least two months ago. I compiled an earlier version of treemacs. I just updated all the packages in emacs a couple days ago, and didn't have any issues. Now all the local variables are missing. It doesn't appear to be a LSP issue, either? In any case, I thought I could get some context in the issue you were having in treemacs? Before, when the local variables would be missing, I'd just step forward a couple of times and they would come in. Now they don't come in at all. :( |
Sorry, for the newbie question. I didn't see an IRC channel for LSP or any reference to this setting in the documentation.
I'm using dap-mode with PHP and Xdebug. My xdebug.var_display_max_data option is set to "-1". I'm still getting a variable cap at around 120 in the locals reference.
Where do we set the display caps for the references in the Locals window for dap-mode? Is that cap coming from another emacs module?
The text was updated successfully, but these errors were encountered: