[Yutaka Emura]

Hello gora,

The default “Courier New” doesn’t support this combining character. Please use a supporting font, for example, Tahoma or Consolas, to show this character.

Thanks.

[Yutaka Emura]

Hello Stefan,

Thank you for showing the screencast. The bug was fixed on beta 2:

https://www.emeditor.com/forums/topic/emeditor-v14-9-0-beta-2/

Thank you!

[Yutaka Emura]

Hi Stefan,

2) It is more complicated that just “only”, and I also found some bugs with the current implementations. I will look into the bugs.

3) I am not sure if I understand the problem. Can you include a sample in this forum, or email me a sample file? I would like to reproduce the problem.

Thanks!

[Yutaka Emura]

Hello Stefan,

As for your first question with the CSV example from Stack Overflow. Embedded newlines mean those M and J reversed symbols (\r and \n characters) in CSV cells. These become embedded in a single line when you switch to a CSV mode, while separated into multiple lines when you switch to the Normal Mode. Does this answer your question?

As for the second question, you should use “version(.|[\r\n])+5” for the regular expression, or check the “Regular Expressions “.” Can Match New Line Characters” check box in the Search tab of the Customize dialog box.

Thanks,

[Yutaka Emura]

Hello,

Currently, there is no option like “auto return to the start of document when I search at the end of the document” for markers.
Is this something you wish to have in future versions? If so, I will consider it in future versions.

Thanks!

[Yutaka Emura]

Hello,

You can use a regular expression. For example:

sys|app

Thanks!

[Yutaka Emura]

Hello LifeTimer,

This feature is added now:

https://www.emeditor.com/forums/topic/emeditor-v14-8-0-beta-1/

Thank you!

[Yutaka Emura]

Hello Mike,

This feature is added now:

https://www.emeditor.com/forums/topic/emeditor-v14-8-0-beta-1/

Join CSV feature.

[Yutaka Emura]

Hello LifeTimer,

This feature is added now:

https://www.emeditor.com/forums/topic/emeditor-v14-8-0-beta-1/

The macro looks like this:

document.Filter("", 0, eeFindRemoveLast);

Thank you!

[Yutaka Emura]

Hello LifeTimer,

You are right. According to WikiPedia, %uxxxx is non-standard implementations. However, is this still common use? If so, I might have to support this.

Thanks!

[Yutaka Emura]

Hello Mike,

Thanks for explanation. This is like the JOINT feature of SQL, and I was thinking about this in future versions. Please wait for future versions.

Meanwhile, you can write a macro like this:

doc1 = editor.Documents.Item(1);
doc2 = editor.Documents.Item(2);
editor.NewFile();
doc3 = document;

doc1.Activate();
nLines1 = doc1.GetLines();
doc2.Activate();
nLines2 = doc2.GetLines();
for( y2 = 1; y2 <= nLines2; y2++ ) {
	doc2.Activate();
	s2 = doc2.GetLine( y2 );
	if( s2 == "" ) continue;
	doc1.Activate();
	for( y1 = 1; y1 <= nLines1; y1++ ) {
		s1 = doc1.GetCell( y1, 1, eeCellIncludeNone );
		if( s1 == "" ) continue;
		if( s1 == s2 ) {
			sResult = doc1.GetCell( y1, 2, eeCellIncludeNone );
			doc3.Activate();
			doc3.writeln( s2 + "\t" + sResult );
			break;
		}
	}
}

Thanks!

[Yutaka Emura]

Hello LifeTimer,

I will look into this issue.
Thank you!

[Yutaka Emura]

Hello Mike,

I am not sure exactly what you want to do. Can you show me an example?

Thank you!

[Yutaka Emura]

Hello,

Since this error happens inside the regular expression engine (Boost regex++), I can’t control what happens inside the regex engine.

What number did you set to the Additional Lines to Search for Regular Expressions text box, and did you set or clear the Regular Expressions “.” Can Match New Line Characters check box?

There might be a different reason so would you send me a sample file (after zipped) to [email protected] along with the Registry file (exported at HKEY_CURRENT_USER\Software\EmSoft, please zip the file)? I will try to reproduce the issue here.

Thank you,

[Yutaka Emura]

Hello LifeTimer,

v14.7.1 beta 2 can now record the filter operations with macros.

There is a breaking change in beta 2, where the second paramter for the Filter method now specifies one-based index of the specified column.

https://www.emeditor.com/forums/topic/emeditor-v14-7-1-beta-1/#post-19743

In case of the example above, you will have to write as this:

document.Filter(document.selection.Text, 0, eeFindKeepPrevious | eeFindNegative);

Thanks!

[Yutaka Emura]

Today, we are releasing EmEditor v14.7.1 beta 2.

Updates from v14.7.1 beta 1 include:

Bug Fixes

• The second paramter for the Filter method now specifies one-based index of the specified column.
• The Record Macro command can now record filtering.
• Russian language files updated.

To Download

http://www.emurasoft.com/pub/beta/emed64_14.7.1_beta2.exe (64-bit)
http://www.emurasoft.com/pub/beta/emed32_14.7.1_beta2.exe (32-bit)

These files will be deleted when official release versions become available. The official releases can be downloaded at the Download page.

How to create portable version:

https://www.emeditor.com/support/#toggle-id-12

Thank you for continue using EmEditor!

[Yutaka Emura]

Hello LifeTimer,

I released a test version of the next version. Please try it and see if macros work as expected.

https://www.emeditor.com/forums/topic/emeditor-v14-7-1-beta-1/

Thank you!

[Yutaka Emura]

Hello,

If you have not already checked, In the Customize dialog box – Search tab, please set:

Additional Lines to Search for Regular Expressions text box to 0

clear the Regular Expressions “.” Can Match New Line Characters check box.

Also, if possible, please re-write regular expressions as simple as possible.

Thanks,

[Yutaka Emura]

Hello LifeTimer,

I understand. I will consider the new option.

Thanks!

[Yutaka Emura]

Hello LifeTimer,

Some people might need to do something between one filter and another filter.

For example,

// first filter
document.Filter( ... );
..  // some operations
// after this another filter
document.Filter( ... );
..  // some operations

Therefore, we have to filter each time a macro find the Filter method. (refresh and actual filter are actually different). A filter operation consumes much time, while refresh is very fast. Nevertheless, I could implement the “eeKeepPreviousFilterLevels” flag instead and make EmEditor macros smart enough to wait actual filtering until the macro see necessary if there is enough reason to do this. I just dont’ want to make the code too complicated.

I didn’t quite understand your sentence:

“because otherwise the “incremental filtering” that I need won’t be possible to implement at all with macros, which would be a real shame, and something that probably many other people than me would miss too in the long run.”

Can you please describe why you need the “eeKeepPreviousFilterLevels” flag instead of the eeFindContinue flag?

[Yutaka Emura]

Hello Edward,

Yes, certainly. With the default keyboard shortcut, you can use CTRL + ] to jump between ( and ), or [ and ], or etc. Its command name is “Find Matching Parenthesis/Bracket”, and you can find in the Quick Launch dialog box (Ctrl + Q) or Keyboard Map.

Thanks,

[Yutaka Emura]

Hello Rien van Ham,

Thanks for letting me know.
With the correct regex, was your issue solved?

[Yutaka Emura]

Hi LifeTimer,

I certainly consider your option before I chose the current “eeFindContinue” flag. That is performance. While it is negligible with small files, if you try to filter a very large file, this makes a big difference. With the eeFindContinue flag, EmEditor will wait until all the filter levels were set before it starts filtering. With the eeKeepPreviousFilterLevels flag, EmEditor will try to filter each time the Filter method appears.

I could implement both flags for conveniences, but I wanted to minimize the number of options.

As I wrote before, there is a bug in the current release (v14.7.0), so please wait until the next version before you start using the Filter method with the eeFindContinue flag.

Thank you.

[Yutaka Emura]

Hello LifeTimer,

I will improve the macro feature so that when a macro is finished with the last Filter method, it will still refresh the documents with the last filter.

Also, I found a bug in the current Filter method with the eeFindContinue flag. So, please don’t use the eeFindContinue flag until the next version.

Thank you,

[Yutaka Emura]

Hello LifeTimer,

If you use the eeFindContinue flag, you have to combine with another Filter method after this. If you need only one level of filter, please use the Filter method without the eeFindContinue flag. So your macro should look like:

document.Filter(document.selection.Text, -1, eeFindNegative);

Thanks,

[Author]

Posts