molsonkiko / JsonToolsNppPlugin

A Notepad++ plugin providing tools for JSON like linting, querying, a tree view, and CSV conversion.
Apache License 2.0
70 stars 9 forks source link

Status bar constantly reverts to JSON #42

Closed vinsworldcom closed 11 months ago

vinsworldcom commented 11 months ago

A little troubleshooting and I think this plugin is causing the issue.

1) Open Notepad++, blank file (new 1) on tab 2) enter the valid JSON {} 3) Plugins => JsonTools => Pretty-print current JSON file 4) close the file - when prompted to save, select "No" 5) File => New

Observe the bottom left status bar now shows "JSON" even though Language menu shows the default "None (Normal Text)" is selected as the file type. Open a close any number of windows and any time a blank window with the "new 1" name is opened, "JSON" shows in the bottom left status bar as the file type.

Can you reproduce this? Any idea what's causing it?

Cheers.

molsonkiko commented 11 months ago

Never noticed this before: good catch!

Yeah, I know exactly what is causing this, and I should be able to fix it soon.

On Wed, Jul 12, 2023, 2:21 PM Vince @.***> wrote:

A little troubleshooting and I think this plugin is causing the issue.

  1. Open Notepad++, blank file (new 1) on tab
  2. enter the valid JSON {}
  3. Plugins => JsonTools => Pretty-print current JSON file
  4. close the file - when prompted to save, select "No"
  5. File => New

Observe the bottom left status bar now shows "JSON" even though Language menu shows the default "None (Normal Text)" is selected as the file type. Open a close any number of windows and any time a blank window with the "new 1" name is opened, "JSON" shows in the bottom left status bar as the file type.

Can you reproduce this? Any idea what's causing it?

Cheers.

— Reply to this email directly, view it on GitHub https://github.com/molsonkiko/JsonToolsNppPlugin/issues/42, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALAQAI3DKQAFSJVEJPN7UC3XP4INZANCNFSM6AAAAAA2IBOXHE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

molsonkiko commented 11 months ago

As far as I can tell, this issue has been resolved by the latest commit.

To avoid similar issues in the future, I made a somewhat larger refactor than was strictly necessary. My testing suggests that this shouldn't lead to any new access violations or other weirdness, but I'm not 100% sure there won't be any going forward.