[Yutaka Emura]

EmEditor now supports DirectWrite on v17.6.0 beta 1.

https://www.emeditor.com/text-editor-features/history/new-in-version-17-6/

Thanks!

[Yutaka Emura]

I added this property to v17.6.0 beta 1.

document.NewLineCode

This is a GET-ONLY property. You can’t use it to set a value.

For example:

code = document.NewlineCode;
switch( code ) {
case eeCrAndLf:
  ...
case eeCrOnly:
  ...
case eeLfOnly:
  ...
case eeNewlineMixed:
  ...
}

[Yutaka Emura]

Hello,

I am not sure exactly what the issue is, so can you please send me a screencast or screenshot to tech @ emurasoft.com? You can also send me sample files (after zipped) with steps to reproduce the issue.

Thanks,

[Yutaka Emura]

Hello Yang Yang,

I will think about that in future versions.

Thanks!

[Yutaka Emura]

Hello,

Please try this:

1. Open all the files you are interested in one group window.
2. Open the Replace dialog box (NOT Replace in Files).
3. Set the “Use Regular Expressions” check box.
4. Set the “Search All Documents in the Group” check box.
5. Click the Down arrow next to the Extract button, and make sure the “Use Output Bar” is set.
6. Enter regular expressions in the Find and Replace text boxes
7. Click “Extract” button.

Thanks,

[Yutaka Emura]

Hello,

I believe all you have to do is:

1. Filter
2. Extract Bookmarked Lines to New File

You might want to record this procedure to a macro.

Thanks,

[Yutaka Emura]

Please try this: go to Customize dialog – Search page, make sure the “Change font for Find/Replace Drop-down List” check box is set, and clear the “Change Font only if Character Set of Selected Font is not System Default”.
Thanks,

[Yutaka Emura]

I reproduced the issue, and it will be fixed on the next version. Thanks!

[Yutaka Emura]

This will be fixed on the next release. Thanks!

[Yutaka Emura]

Thanks for information. This should be fixed on beta 3, which I released today.

[Yutaka Emura]

Hello,

I couldn’t reproduce the issue, and it might be due to your particular settings. Please zip a crash report file along with your settings (including AppData folder) exported from Tools menu > Import and Export > Export all settings into a registry file. You can email the file to tech @ emurasoft.com

Thanks,

[Yutaka Emura]

Please use this registry technique to work around in your case.
Yes, the icon is correct, it is a triangle shape.
It is NOT unusual to use DWORD for 64-bit apps..

Thanks,

[Yutaka Emura]

Please try v17.5.0 beta 1 (17.4.901) which I released today. If this still doesn’t work, please open regedit.exe, and create a new REG_DWORD value “AltNodeImage” in the HKEY_CURRENT_USER\Software\EmSoft\EmEditor v3\Common key, and assign the value 1 to it. Thanks,

[Yutaka Emura]

Opening the same file in several EmEditor windows is NOT supported.

Thanks!

[Yutaka Emura]

What kind of theme do you use in the Display properties of Windows? Please try resetting the theme.

You can also try Classic Theme, which causes EmEditor to use an alternate node image for Outlining.

[Yutaka Emura]

Are you using Remote Desktop and connect to your machine remotely? I reproduced the issue by using Remote Desktop.

[Yutaka Emura]

I don’t see this issue anymore maybe because of Windows updates. Can you update your Windows (please apply all available updates), restart Windows, and try again?
Thanks,

[Yutaka Emura]

Hello,

It depends on how those words are highlighted. If they were highlighted exactly the same way as misspelled words, EmEditor will NOT figure out which text are misspelled words, and currently this is limitation of EmEditor. If this is important, I might have to look into the issue. If you are NOT sure what I mean, please send me a screenshot so that I can figure out exactly what the issue is.

Thanks,

[Yutaka Emura]

This seems a Windows 10 issue. I will address this issue on the next version.

Thanks,

[Yutaka Emura]

Hello LTT,

I can’t reproduce the issue. Which version of EmEditor are you using? If you are not using the newest version, please update to the newest version. Portable version or Installer version? It is possible that either configuration A or B was corrupted. Can you try another configuration to reproduce the issue?

Thanks,

[Yutaka Emura]

Hello,

I am not sure what the issue is. How exactly can’t you easily return to normal mode?
Are you using the newest version of EmEditor?

[Yutaka Emura]

As of the current version of EmEditor, the condition to trigger this prompt is supposed to be 0x08000000 (134,217,728) characters or more exist in one line.

[Yutaka Emura]

Hello sky,

This is a bug, and I will fix that on the next minor version. Meanwhile, you can set the Do not show this message again option in this dialog box, or Prompt when Very Long Lines Exist check box in the Edit page of the Customize dialog box.

Thanks,

[Yutaka Emura]

Currently, it is not possible to define several root folders in the Explorer plug-in. If this is important, and if the Explorer plug-in is right for you, I can think about adding the ability to define several root folders to the Explorer plug-in.

[Yutaka Emura]

EmEditor does NOT use such APIs. The Windows build 17063 is yet in Preview Build, and has NOT been officially released. I imagine any issues will be resolved by the official release.

[Author]

Posts