Can not reload error.e in v14.0.2.2?

[Ding Zhaojie]

I patched something in error.e, but I found I can not reload it. After I executed the command "load error.e", it says "Module(s) loaded", but my modifications did not applied. I tried to unload error.ex, but it says "Cannot remove module". How to solve this and make my patch work?

[ScottW, VP of Dev]

Please post the specific steps you used to load and unload the updated file. The more detail you include, the more likely someone will be able to help. How did you determine your modifications were not applied?

Instead of unloading error.e, try reloading the original, unmodified version. As a best practice, you should not modify the .e files in the macros subdirectory. Copy the file to a different location and modify it. That way you preserve the original as a baseline and can easily diff them to see what you changed.

Also, remember that loading a macro file only changes the config you load it in. If you have multiple configs, you have to load the modified file in each one.

Finally, be sure to keep a version of SlickEdit around without the modified files so that when problems occur you can see if they are because of your modifications or if they occur in the as-shipped version of SlickEdit. You can do this by using -sc to setup a clean config somewhere as long as you put your modified files in a different directory.

[Ding Zhaojie]

The mod I made to error.e is very simple, just let it activate messages window if there were something wrong in building:

at the end of set_error_markers():

Code: [Select]

  if (err_count > 0) {
       activate_messages();
   }
Then I just save error.e, and load it with the load command (I also tried the gui-load). That's all, this simple mod did not work. So I add a say("Hello!") at the beginning of set_error_markers(), then load and run set-error-markers, nothing printed.

I tried the -sc to start with factory settings, then load the error.e again, and seems the mod did not be applied after loading the error.e, too.

[jero]

Any progress on this?
I have the exact same problem in 14.0.2.2, actually I even tried deleting everything in error.e, reload it, and nothing breaks.
The previous version I used (12.x) was fine.

[JakeMontgomery]

Any progress on this? I have the same issue with 16.0.3.0