You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In notepad++, all plugin configuration files are at: %appdata%\Notepad++\plugins\config
I think that emmet should also place its configuration and user files there, in a directory like: %appdata%\Notepad++\plugins\config\emmet
There, is where all user changeable files like the snippets.json should be, not in the notepad++ directory.
One main reason for that is that the contents of program files (and program files (x86)) are usually not part of backups routines (just like in my case) as most programs have to be reinstalled if they are transfered to a different computer.
That while also being dispensable, as the install is in a CD (or equivalent) or can be downloaded from somewhere. Also, notepad++ installs, by default, in there.
Note: This applies only if notepad++ was installed with the configuration to store data inside %appdata%. Otherwise, I don't know how it should behave.
In notepad++, all plugin configuration files are at:
%appdata%\Notepad++\plugins\config
I think that emmet should also place its configuration and user files there, in a directory like:
%appdata%\Notepad++\plugins\config\emmet
There, is where all user changeable files like the snippets.json should be, not in the notepad++ directory.
One main reason for that is that the contents of program files (and program files (x86)) are usually not part of backups routines (just like in my case) as most programs have to be reinstalled if they are transfered to a different computer.
That while also being dispensable, as the install is in a CD (or equivalent) or can be downloaded from somewhere. Also, notepad++ installs, by default, in there.
Note: This applies only if notepad++ was installed with the configuration to store data inside %appdata%. Otherwise, I don't know how it should behave.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: