[Yutaka Emura]

Hello,

I optimized the speed while filtered on beta 3.

Thank you!

[Yutaka Emura]

Hello voiid,

This will be fixed on the next version, beta 3.

Thank you!

[Yutaka Emura]

Hello,

Beta 2 shows a separator line between separated blocks after filtered, and you can change the color and style of the lines in the Display tab of Configuration Properties, select User-Defined Guides in the Specify Part list box, and select Text Color or Style.

Thanks,

[Yutaka Emura]

Hello Bogumil,

I reproduced the issue, and I will look into the issue. However, this is just because EmEditor tries to locate a correct line location from filtered documents, and lots of calculations are involved. You might want to extract all filtered lines to a new document by clicking the “Extract All” button on the Filter toolbar after you filter a document, or you can go to the Find dialog box, and use the Extract All button. Then you can work much faster with the newly created document.

Thanks,

[Yutaka Emura]

Hello LifeTimer,

On the next version (v16.2.0 beta 2), you can use eePosCellView flag to specify the coordinate in Cell View mode. For example:

document.selection.SetActivePoint( eePosCellView, 1, 7, false );

will set the active cell at (1,7) in the view.

Thank you,

[Yutaka Emura]

Hello LifeTimer,

Thanks for clarification.

You can use:

editor.ExecuteCommandByID(4461);

to select the current column without headings.

Thank you,

[Yutaka Emura]

Hello,

document.GetLines(eeGetLineView);

should always return the number of only visible lines. Please make sure you add the “eeGetLinesView” flag as written above.

Can you make sure you use the latest version of EmEditor?

If the problem persists, please write the issue with a very simple example with a few sentences (as simple as possible).

Thank you,

[Yutaka Emura]

It should be:

editor.ExecuteCommandByID nID

I will fix this documentation.

Thank you!

[Yutaka Emura]

Hello,

I will think about adding macro object/methods/properties related to markers.

Meanwhile, you can use the Add to Markers command:

editor.ExecuteCommandByID(4560);

I hope this helps.

Thanks,

[Yutaka Emura]

I will certainly think about that in the future.

Thanks,

[Yutaka Emura]

Hello LifeTimer,

The following macro should get the number of visible lines.

n = document.GetLines( eeGetLineView );

Can you please try and let me know if you have further questions?

[Yutaka Emura]

Hello JohnQSmith,

You are right. I will update the color themes.

Thanks!

[Yutaka Emura]

Hello sky,

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

Thanks,

[Yutaka Emura]

To delete blank lines, I would bookmark all regular expressions:

^$

(use “Bookmark All” button in the Find dialog box)

and then use the Delete Bookmarked Lines command.

If you have enough physical memory in your PC, and if you need to replace many multi-line text (combine lines or split lines), you might want to try clearing the Use Temporary File to Reduce Memory Usage check box in the Advanced tab of the Customize dialog box.

Thanks,

[Yutaka Emura]

Hello,

I am not sure if it is called a bug, but I will think about that in future versions.
Thanks,

[Yutaka Emura]

Hello,

These plug-ins uses certain Windows API functions to do these conversion. You can download the source code from our library, and customize the plug-ins as you wish.

Thanks,

[Yutaka Emura]

Hello,

I understand what you mean. However, the current behavior of EmEditor is correct. The hidden line is only HIDDEN, and not DELETED. Therefore, when you do a search, EmEditor will do the search according to the real text. EmEditor will only skip hidden lines if the search term doesn’t begin with the visible lines, but once the visible portion matches, EmEditor will check the hidden text. If you really want to delete those lines, you should extract filtered text into another document (You can use the Extract All button in the Filter toolbar). The logic is similar to hidden text by Outline Guide. It is also similar to the result of “Compare” commands. After comparison, some lines are separated by blank lines, but the search will not consider them real blank lines.

If this contradicts any other behaviors of EmEditor, please let me know.

Thank you,

[Yutaka Emura]

Hi Paul,

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

Thanks!

[Yutaka Emura]

Yes, I try EmEditor use very little memory per line, and one flag per line is very significant increase.

I am not sure if I understand your question about filtering. If this is a bug, can you please write a simple test case so that I can reproduce the issue.

Thank you,

[Yutaka Emura]

Hello,

In order to highlight multi-line search terms, EmEditor will need additional flags for each line, which increases memory usage. It also increases the computation time, and slows down the EmEditor speed. Therefore, EmEditor does not highlight multi-line search terms, and it has been this way for many years.

I understand the filtering out means. Thanks for clarification.

[Yutaka Emura]

Hello,

You can use:

document.selection.GetActivePointX( eePosCell );

Thanks,

[Yutaka Emura]

Hello,

EmEditor will not highlight (green) if the highlight word contains a newline. The Filter feature will not search for a newline.

I hope this clarifies your question. Please let me know if you can’t really find any regular expressions.

Thanks,

[Yutaka Emura]

Hello jic,

I understood.
Please make sure a backslash (\) is specified in the Escape Character text box in the Highlight (2) tab of configuration properties.

Thanks,

[Yutaka Emura]

Hello LTT,

I will look into these issues. There are no macro functions available for markers.

Thanks!

[Yutaka Emura]

Hello,

Can you please explain what the problem is? Is this about CSV documents, or highlighting problems?

[Author]

Posts