-
Notifications
You must be signed in to change notification settings - Fork 10
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
always getting "no input at position 0" (TRY INSTALLING V5.6+, SEE IF THAT FIXES IT) #16
Comments
Hi igpit, that's very strange! As I noted in response to issue #17 , I have not observed any unusual behavior when running JsonTools with the same setup as yours except for the differences noted in my first comment there. Does this happen on all JSON files that you try to use it for, or can you show me examples where it does and doesn't fail? |
Thanks for sticking with me despite this frustrating issue! I've tried playing around with the encoding of an example MS Teams desktop-config.json, and I even temporarily set my system language to German to see if any of those changes caused a similar error a similar document that the plugin previously handled fine. No change short of manually inserting a bad character has done anything. |
it seems not to be related to any json content. this even happens with a empty document. |
I just tried install JSON Viewer and JSTool and none of them interfere with this plugin in any way (aside from making Alt-based keyboard shortcuts harder to use). I'm not going to close this issue, but I really have absolutely no idea how to solve this problem, because I can't replicate it on my machine. At one point I tried spinning up a Windows AWS instance to see if I could replicate it elsewhere, but:
If some other developer who can replicate the issue wants to fix this problem for me, I'd be delighted. But I can't help you. In light of this, I recommend that you look at some of the alternative tools I've listed in the README. All of them seem based on my testing to work fine. |
If anyone who's had this issue feels like pursuing it further, maybe they could leave their computer's debug info ( For the record, here's mine:
|
How can i solve this problem? I am having the same problem. |
Hi all, I think I may have solved it (fingers crossed!) A bug that was making this plugin incompatible with Notepad++ older than 8.4.1 was fixed, and that may have been what was going wrong for you. Try the DLLs here: |
Debug info as requested.
EDIT: Ignore this. I just installed this tool today, but it installed 4.4???? Notepad++ now shows an update to 5.6 which does resolve the issue for me. |
ctidrv said
Thanks so much for letting me know that, @ctidrv ! Anybody else having this issue: try upgrading to release 5.6, or better yet, the latest release. I'd be interested to see if this issue is fixed for other people as well! I'd also be curious to know what was the earliest release where this was fixed, though I certainly don't expect anyone to do this for me. |
Can confirm updating solved the issue for me. Started randomly getting this error a week or two ago. I noticed I was on JSON Tools version 4.X.X, and Notepad++ version 8.4.X. There was not a way to update to JSON tools 5.6, so I just unistalled the plugin, updated NPP to 8.6, and I was able to reinstall the JSON Tools plugin @ version 5.6 and issue went away! Thanks! |
open json text file, do something from JsonTools menu, e.g. pretty print or show tree
Could not parse the document because of error
no input at position 0 (char '
using npp 8.4.6 with latest jsontools, in "C:\Program Files\Notepad++\plugins\JsonTools\JsonTools.dll"
The text was updated successfully, but these errors were encountered: