With your description I may be able to make another version and test.Īt the moment I’m inclined to think it’s the idea behind the macro that’s flawed, not the engine running the macro.
This is probably going to be a bit of a long shot as macro code is very hard to read. This will make it show as per my example above (in a black box). When inserting the macro code into here, put a blank line before and 4 spaces on the line before inserting the code.
Depending on whether you installed the 32bit or 64bit Notepad++ program it could be in either of the 2 Program FIles folders (you can only install 64bit version if Windows is also 64bit).Ĭould you supply a description of what you intend the macro to do? You might also want to grab that portion from the shortcuts.xml file since you seem to have saved it. Try the C:\Program Files\Notepad++ folder or C:\Program Files (x86)\Notepad++ folder. There are 2 locations that the shortcuts.xml file resides in, Notepad++ could be using either one, depending on how it was installed. Also see if the macro is listed when reloading Notepad++. Start Notepad++, do your test macro, save it then exit, it should recreate the file. If you are able to successfully edit it, then delete the file (you still have the backup). Regardless which is the problem I’d make a backup of that file (in both locations, see below), then attempt to edit the file first. If the macro is not listed then the shortcuts.xml file is corrupt or you don’t have permisssions to edit that file. At this point I don’t care if the macro works, just if it exists in the menu option. So following my instructions, if you ‘saved’ the macro and it successfully wrote the macro to 1 of 2 shortcuts.xml files, then by exiting and reloading Notepad++ you should see the ‘test’ macro listed under the Macro menu option.
This file could be in multiple locations but the default is C:\Users\YOUR USERNAME\AppData\Roaming\Notepad++
Have you checked in the shortcuts.xml file to see if the macro has indeed saved there. Taking the steps above helps to break down the issue, confirming along the way that you building on a solid foundation. Without seeing the macro it’s hard to say where the error lies. You may need to take it in steps, confirming along the way that the macro does work. Then move onto the more complicated macro creation. If you can get that working then you’ve established the steps you are taking are correct. My first suggestion would be to create a simple macro, save it and then test.