[axial]

Update:
The hung installation resulted in not being able to reboot using the normal Windows Restart process. It was impossible to know from Task Manager which was the install program in order to terminate it there, so I ended up having to use the reset button.

After reboot I temporarily disabled NOD32. Add/Remove programs did not show EmEditor as being installed.

I double-clicked on the install msi and the dialog said that the installation could be continued, so I chose yes. It continued and did complete installation. EmEditor seems to be correctly installed.

If I can provide any other troubleshooting information just let me know.
Thank you.

[axial]

Adding my urgent vote for this capability.

I hadn’t noticed that custom backup naming was not possible when I did the evaluation, and now I’m finding it almost impossible to use EmEditor in my workflow where I often have other scripts that process files using exclusions to ignore specific backup naming patterns.

My preference would be two-fold:

a) have the choice of whether to use multiple numbered backups or just a single backup

b) to have the choice of naming conventions such as:

file.bak
file.bak.ext
file.ext.bak
file.ext in folder xxyy

[Author]

Posts