[Yutaka Emura]

Hello,

This will be fixed on v13.0.4.

Thanks!

[Yutaka Emura]

Hello dmitryl,

EmEditor can open a file as READ-ONLY if the file has READ-ONLY attributes. That’s the only way you can open files ALWAYS as READ-ONLY. If this is a feature request, I will consider it in future versions.

Thanks!

[Yutaka Emura]

Hello,

If you using the 64-bit version of EmEditor, you will have to use the 64-bit version of ActiveScript. Can you please make sure the ActiveScript you are using is 64-bit? If the 64-bit version is not avaialble, you will have to use the 32-bit version of both EmEditor and the ActiveScript.

Thanks!

[Yutaka Emura]

Hello,

This is the screenshot in my case:

 

How would you like to change this?

Thanks!

[Yutaka Emura]

Hello,

Can you try this if you haven’t tried: Please go to the Outine plug-in properties, and click “Reset” button. Then you can change the settings to your needs.

Thanks!

[Yutaka Emura]

Hello,

Yes, I will add the new property on future releases. Thanks!

[Yutaka Emura]

No, it is not supported. I will consider this in future versions.

Thanks!

[Yutaka Emura]

Hello LTT,

This is currently by design, but I will make the sort command possible even if another window opens a dialog box in future versions.

THanks!

[Yutaka Emura]

Hello,

I adjusted the drop-down list box font size in the Find toolbar as well. I will release the next minor version shortly.

Thanks!

[Yutaka Emura]

OK. This depends on fonts. Can you please try Consolas?

Thanks!

[Yutaka Emura]

Hello mguttman,

A limitation was necessary to keep EmEditor run faster. I am changing the limit to 10,000 characters long (this is the same as the Find string in the Find dialog). This applies to both the Auto-marker and normal markers in the list.

I read your other requests, but these are a little difficult to address. I might consider these in future versions.

Thanks!

[Yutaka Emura]

Hello thanksgod,

If you change the Registry values, you will have to restart EmEditor. In my experiments, if I set UseWidthArray as 1, the Thai character shows OK, although selecting and editing characters do not work well. On the next minor version, I handled this special character differently, so it should work better. So, please remove the UseUniscribe and UseWidthArray values before you try the next minor version. If there are any other issues with Thai, please let me know.

Hello mguttman,

I tried the combination of ĉb, but I didn’t see any issues. It may be because of the different OS, different version of EmEditor, or some old Registry values. What OS do you use, and which version of EmEditor do you use? If you add any Registry values, can you please remove those values?

Thank you!

[Yutaka Emura]

Hello,

Did you try both 1 and 0, which makes 4 combinations in total?

Thanks!

[Yutaka Emura]

Hello,

Yes, but I will remove this length limit on the Auto Marker on the next minor version. All other markers will still have length limitation of 79 charcters long.

Thanks!

[Yutaka Emura]

Hello,

OK. I will fix this issue on the next minor version.

Thanks!

[Yutaka Emura]

Hello,

Can you try settings the UseUniscribe value in the Registry as below? You can also try changing the UseWidthArray value:

HKEY_CURRENT_USERSoftwareEmSoftEmEditor v3Common

UseUniscribe DWORD default: 1 for Windows XP, 0 for Windows Vista or later

UseWidthArray DWORD default: 1

Thank you,

[Yutaka Emura]

Hello,

I can’t reproduce the issue, but I believe there is a condition. Can you please export your settings from the Registry (HKEY_CURRENT_USERSoftwareEmSoftEmEditor v3), zip the files, and email to [email protected], and please identify yourself that you are gan from the forum.

Thanks!

[Yutaka Emura]

Hello,

I see. I will have to consider improvements about line comments in future versions. For example, using regular expressions to specify line comments.

Thanks!

[Yutaka Emura]

Hello,

I realize this issue. It will be fixed by today’s update (v13.0.1), and it will be released shortly. Thanks!

[Yutaka Emura]

Hello,

Please use a fixed-pitch font, not a proportional font!

Thanks!

[Yutaka Emura]

Hello ginger,

In recent versions of Windows, Ctrl+Shift+0 is by default used by Windows, so it can’t be used by EmEditor even though EmEditor set this shortcut correctly.

Please see:

http://support.microsoft.com/kb/967893

to remove this shortcut assignments from Windows.

Thanks!

[Yutaka Emura]

Hello,

You probably used the portable version of EmEditor. If you use the installer, the installer will warn you about the new key requirement during the installation, and there is 30-day grace period. However, if you just overwrite files using the portable version, there is no way for EmEditor to detect when you started to use v13, and EmEditor won’t be able to give you a grace period. Please use the Installer version whenever possible.

Thank you,

[Yutaka Emura]

Hello Andreas,

I see. I believe some users still want the current behavior, so I will have to add new commands. I will add these new commands in future versions.

Thank you,

[Yutaka Emura]

Flint wrote:
Thank you, it would be helpful. I didn’t think about such possibility.

BTW, how do you access these options? I don’t see them in the reference. Or did you mean a macro that will send specific keypresses for opening the dialog and ticking the checkbox?

Hi Flint,

I thought it was possible by doing this:

n = editor.GetProfileInt( eeRegCommon, "", "EnableMultiSel", 1 );

	editor.WriteProfileInt( eeRegCommon, "", "EnableMultiSel", !n );

	

But this code doesn’t work actually. It is because EmEditor has to be refreshed with new Registry values.

I might add a feature to refreh EmEditor or ability to toggle the Mulitple Selection option in future versions.

Thanks!

[Yutaka Emura]

Hi David,

Yes, that’s correct.

[Author]

Posts