Forum Replies Created
- Posts
Hello gordy,
We are just updating to new minor versions mainly to fix new bugs. (v12.0.0 -> 12.0.4) I realize some people do not appreciate these minor updates but we need to offer updates in order to resolve some customers who really need bug fixes and stability. I hope we don’t have to make updates any more until the next major version.
Thank you!
Hello,
This seems like the Matching Tag Highlight feature of v12. You might want to clear the Highlight Matching Tag check box in the Highlight (2) tab of configuration properties if it is checked.
Hello,
You might want to check “Save Cursor Position and Bookmarks” check box on the File tab of the Customize dialog box.
Thank you!
Hello ArthurZ,
In order to reproduce the issue, can you please email me the following files (after zipped) at [email protected]?
– Please export your settings by selecting “Import and Export” on the Tools menu, select “Export all settings into a registry file”. You will find the exported .reg file.
– A sample SQL file that you can reproduce the issue.
Thank you!
Hi,
The only way to find edited lines are that line numbers become highlighted (bold style) when the Line Number (on View menu) is checked.
Other than that, there is no way to indicated edited lines or saved lines. I will consider this in future versions.
Thank you!
Hello LTT,
This is just because “H” is a part of “H_r”, and so “H” is matched before “H_r” is matched. This is the expected behavior.
Hello LTT,
I noticed this is a bug of the Properties of the HTMLBar button. Currently, you will have to select “Customize” on this Special Command drop-down list in order to add the Font button. I will fix this by the next minor version.
Thank you!
Hello,
The current version doesn’t support such a feature, except for making a macro or snippet for that purpose and assign that macro or snippet as BACKSPACE. I will think about that in future versions if this is important to you. You can also use SHIFT + TAB to delete tabs after selecting the lines you want to remove indent.
Thank you!
Hello,
The issue is that if the Find Bar or Find dialog box is visible, the contents in the Find Bar or Find dialog box has higher priority to determine the search string when F3 is pressed. I will try to synchronize the contents of Find Bar when this macro is run on the next minor version. Meanwhile, please hide the Find Bar.
Thanks!
Hello mcdgfd,
Thank you for all the information you have sent me! That was very helpful.
As I emailed, I believe I found the bug. Please try clearing the “Save Cursor Position and Bookmarks” check box on the File tab of the Customise (or Customize) dialog box (on the Tools menu > Cutomise (or Customize)).
When this is checked, there is a bug when saving bookmarks even though there is no bookmark set.
Please let me know if this eliminates crashes.
Thank you!
Hello mcdgfd,
Dr. Watson log should be left on your system and it won’t be erased automatically. The log file should be
C:Documents and SettingsAll UsersApplication DataMicrosoftDr Watsondrwtsn32.log
If you find this file, please send it now.
If you don’t find this file, you might need to fine-tune the settings according to this FAQ before you encounter another crash:
http://www.emeditor.com/modules/xoopsfaq/index.php?cat_id=13#q93
I am looking forward to your information.
Thank you!
Hello JohnQSmith,
I am trying to reproduce the issue, but I couldn’t.
Are you using the latest version (v12)?
Can you write the procedure step-by-step to reproduce the issue?
Thank you!
Hello,
Since you are using Windows XP, you can get Dr. Watson log and send it to me. To get Dr. Watson log, please see:
http://www.emeditor.com/modules/xoopsfaq/index.php?cat_id=13#q93
You can zip the log, and send it to me as an attachment ( [email protected] ).
Those who use Windows Vista and later, EmEditor v12 now leaves crash report files at C:ProgramDataEmurasoftEmEditorError .
However, Dr. Watson log has more detail information than my crash reports, so I prefer Dr. Watson log if you run on Windows XP.
This issue is very important, and I really want to fix this bug. I am looking forward to your email.
Thank you!
Hello,
Our statistics show very few people use the 64-bit version of Windows XP, so I optimized the 64-bit EmEditor for Windows Vista or later using the latest version of Visual Studio. The latest version of Visual Studio doesn’t support Windows XP or earlier. The 32-bit version of EmEditor is compiled by an old version of Visual Studio to make EmEditor compatible with Windows 2000 and XP. Please consider using the 32-bit version of EmEditor, continue using EmEditor 11.0.5, or use the 64-bit version of EmEditor on Windows Vista or later (64-bit).
Thank you!
