[Yutaka Emura]

I addressed these issue on v17.1.2.
Thanks!

[Yutaka Emura]

All macros that have :

Filter( document.selection.Text ...

are affected. Please wait until v17.1.2 is released. I also recommend you updating EmEditor every time a new version is released.
Thanks!

[Yutaka Emura]

This will be fixed on the next version.
Thanks!

[Yutaka Emura]

Hello LifeTimer,

I am sorry that I misunderstood your question. Unfortunately, there are no good ways to pass parameters from commandline to macros. To work around this, you can use an external file or registry values to pass parameters. For instance, you can write data to an external file, and then you can read that data in the macro. You can also use a registry value to pass data.
I hope this helps.

Thanks,

[Yutaka Emura]

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

[Yutaka Emura]

Hello,

Please use ExecuteMacro method to run a macro within a macro. Does it work for you?

Thanks,

[Yutaka Emura]

I reproduced the issue on the latest version, and it will be fixed on the next version.
By the way, this issue has existed for a long time since v16.2 or v16.5.

Thanks,

[Yutaka Emura]

Hello,

I just want to confirm, but are you using the latest version of EmEditor (v17.1.1)?

Thanks,

[Yutaka Emura]

Hello,

I believe this bug was fixed on the latest version (v17.1.1). Can you make sure you are installing the latest version?

Thanks,

[Yutaka Emura]

The Problem 1 will be fixed on the next version.

The Problem 2 is actually NOT a bug, but it is how EmEditor works.
When you enter a string in the Cell toolbar, EmEditor automatically converts the string according to the CSV rule described in:

https://en.wikipedia.org/wiki/Comma-separated_values

I hope this helps.

Thanks,

[Yutaka Emura]

This issue will be fixed on the next version.
Thanks!

[Yutaka Emura]

This issue will be fixed on the next version.
Thanks!

[Yutaka Emura]

Hello LTT,

All these issues will be fixed on the next version.
Thanks!

[Yutaka Emura]

The Pin to this (favorite) list, and Unpin from this (favorite) list commands were NOT enabled for workspaces, but I will fix other issues on the next version.
Thanks,

[Yutaka Emura]

This will be fixed on the next version.
Thanks,

[Yutaka Emura]

This will be fixed on the next version.
Thanks!

[Yutaka Emura]

Hello,

“CWP” is NOT related to macros.
Currently, there is no way to enable/disable another macro’s “Runs at Events” settings, unfortunately. I am not sure why you need to enable/disable another macros’ event settings. Maybe, you might want to explain why, and I might think about workarounds.

Thanks,

[Yutaka Emura]

This issue will be fixed on the next version. Thanks!

[Yutaka Emura]

This issue will be fixed on the next version. Thanks!

[Yutaka Emura]

Can you show me the screenshot of Windows Task Manager > Performance tab > Memory after you open the very large file but before you Replace All?

[Yutaka Emura]

This will be fixed on the next version.
Thanks!

[Yutaka Emura]

Good finding! I will fix that on the next version.

[Yutaka Emura]

Hello,

I am sorry for inconveniences. The Runs at Events issue will be fixed on the next version (v17.1.1). Meanwhile, you can work around by adding a new registry value:

UsedEvents

as REG_DWORD at HKEY_CURRENT_USER\Software\EmSoft\EmEditor v3\Common, and set the value as 0xffffffff in hexadecimal (or 4294967295 in decimal).

Notes that this workaround will NOT be needed anymore once v17.1.1 is released and installed.

Thanks,

[Yutaka Emura]

This will be fixed on the next version. I wonder how you came across this bug!

[Yutaka Emura]

This will be fixed on the next version.
Thanks!

[Author]

Posts