EmEditor Professional 22.5.0 (64-bit)

What's new in this version:

- I recently bought a PC with a 13th Gen Intel Core i7-13700. Since the 12th Gen Core processors, Intel has introduced a hybrid architecture that combines P-Cores for performance and E-Cores for efficiency. This new architecture is interesting because a P-Core runs faster than an E-Core. All previous versions of EmEditor assumed that all threads run at the same speed. If a P-Core thread runs faster than an E-Core thread, P-Core threads finish their task earlier than E-Core threads and need to wait for E-Core threads to finish their task. Just for clarification, thread speed could fluctuate even without E-Cores and P-Cores; for instance, if a thread is interrupted by a background app or system process, the thread will become slower than other threads. Nevertheless, the existence of P-Cores and E-Cores could exacerbate the situation.
- To overcome this situation, I optimized the code so that v22.5 will dynamically manage thread load balancing. The following screenshots show the CPU usage before and after optimization while searching a very large file for a regular expression. The overall CPU usage goes down suddenly at the end of the task after optimization.
- The new version (v22.5) dynamically manages the thread load balancing so that every thread works efficiently until the task ends. The overall CPU usages goes down suddenly at the end of the task. As a result, the time to finish the task becomes shorter.
- While developing v22.5, we spent most of our time optimizing our code to improve the speed of many commands using various techniques, including multi-threading. For instance, the speed of the Copy command was improved by 1.49 times through multi-threading. While refactoring and optimizing, I had opportunities to review the code. The older version inadvertently did not enable the SHA instruction set if the CPU did not support the AVX-512 instruction set. v22.5 fixed this bug and improved the speed of several commands, including Delete Duplicate Lines, on many CPUs that do not support AVX-512. I will continue to review and optimize the code for speed in coming versions.
- When I first used my new PC to build our code with Visual C++, I was disappointed to know that the build was very slow. We found that the memory usage reached 100% when building the code because only 16 GB of physical memory (RAM) was available. The CPU has 24 logical cores, and Visual C++ was using 24 threads to build the code. Adjusting the number of threads from 24 to 7 in the Visual C++ options made the compiler build the code faster. Likewise, EmEditor was slower when using 24 threads compared to 3 threads. Increasing the physical memory from 16 GB to 80 GB made both apps faster with 24 threads. Therefore, if you have a modern CPU with a large number of logical cores, I would strongly recommend increasing the physical memory. For instance, if your CPU has 24 logical cores, I would recommend at least 32 GB of physical memory in your PC. If you don’t have enough memory, you might need to adjust the number of threads, which can be specified on the Advanced page of the Customize dialog box in EmEditor. In v22.5, I adjusted the default number of threads to the nearest GB amount of physical memory if the number of logical cores exceeds this GB value.
- A customer asked for an improvement in file change detection. The older version checked the current file size and timestamp every 5 seconds by default, and if it determined that the file had changed, a message box “File changed by another program. Reload with changes?” would appear. v22.5 uses a Windows API to detect file changes more efficiently.
- Another customer asked for the ability to click on the left edge of a line number to toggle the bookmark. With older versions, you would have had to select the Toggle Bookmark command or press CTRL + F2 to toggle the bookmark. I understand that clicking on the line number would be easier and somewhat standard among text editors, so I added this ability if line numbers are visible.
- Makoto Emura added the ability to use the Language Server Protocol for the Search Symbols command and the ability to use the JSON language server. He also improved the CommitList plug-in by adding commits ahead/behind indicators for the Pull and Push buttons.
- We will stop supporting Windows 7, 8.1, and Server 2008 R2 in the near future. Microsoft has already stopped supporting these versions of Windows. Using these old versions of Windows is strongly discouraged for security reasons. We will also stop developing the 32-bit version of EmEditor. We would like to focus our development and testing resources on the 64-bit version of EmEditor.
- Since we want many people to use EmEditor, we have kept our EmEditor price as low as possible. The first-year price of an annual subscription, US$40 (or US$39.99 earlier), has not changed by more than 1 cent since we started offering annual subscription licensing. However, we do not tolerate the illegal use of EmEditor Professional. I have seen some websites selling or giving away EmEditor Professional “crack” keys. These are illegal sites, and keys obtained from these sites are not supported by us. I sometimes receive technical questions about EmEditor Professional even though the users do not have valid licenses. I would rather spend my time supporting our customers who have purchased valid licenses. In order to eradicate these illegal sites, and more importantly, to continue developing EmEditor and supporting our customers, we will add code to check the authenticity of licenses against our server database. If a license is not valid, the code will stop the Professional version from working. This check may not happen as soon as you launch EmEditor, and it may not happen every time you launch EmEditor. Due to the nature and purpose of this code, we will not disclose details about how it works. However, no personal information will be transmitted, and this check will not prevent you from using EmEditor without an Internet connection. It is important for us to protect our software and our customers who have purchased valid licenses. I hope you understand the background reason for this minimum license check and accept it. Please also see How to calculate the number of licenses to check whether you own enough necessary number of licenses.