[spiros]

My usual workflow was to select some consecutive filtered lines (not full filtered text) and then apply the case change, would this still affect the non-filtered lines inbetween?

[spiros]

Yes, but that does not make sense (it is not intuitive), only visible (filtered) text should be affected.

Thanks for the workflow, but my example was just to point out the issue, I would need to change case in pretty varied scenarios.

[spiros]

I am working with a 500.000 lines file and Option 2 apparently works (in my case does not work at all, see screen) if “Word Count” plugin is active, which means… very slow performance. It was dead slow even with a 30.000 lines file.

[spiros]

Option 1: Takes ages to load…
Option 2: always shows the total number of lines for FULL file

[spiros]

This did it for me

^[Α-ΩΆ-ΏA-Z]

(I had to add “Ά-Ώ” so that it would get capitals with accents too)

Is there a way to show the number of lines filtered?

[spiros]

This is the way used by Notepad++
https://www.translatum.gr/forum/index.php?topic=470680.0

Maybe something similar could be done?

[spiros]

Suppose you have enabled “Treat CR and LF Separately” in Advanced dialog box,

Yes, that was the problem.

[spiros]

Try this text:

Can you please describe
more details, and include
a sample file, so that
we can reproduce the issue?

Find: \n
Replace: ,

Result:

imgur.com/a/Q2bCq

Can you please describe
, more details, and include
, a sample file, so that
, we can reproduce the issue?

Instead of:

Can you please describe, more details, and include, a sample file, so that, we can reproduce the issue?

[spiros]

Thanks, I was trying to find some indication of “Filter” on the menus, (I.e. Search) but there was none. Maybe increase discoverability of this feature?

[spiros]

Great one, sky, thanks!

[spiros]

Maybe I was wrong, it was some Greek text that I had used with extra diacritics.

[spiros]

When I tested with a 50.000 line document, it took a lot of time and when it was done, it froze. v17.1.0 beta 2

I tried this instead which worked in an instant:

(^.*)(\t)
\1:

[spiros]

Good suggestion, sky. Things like that should work out of the box for a fast editor -:)

[spiros]

Thank you.

[spiros]

Thanks!

[spiros]

Thanks! Well, I still think it would be more intuitive as a “Count” button below “Find Next” for example. Now one has to check the box and then click “Find Next” and then uncheck the box.

[spiros]

Wow, it worked in 2 seconds! Thank you so much.

Perhaps you could consider adding it as a sorting function in the “Separated values/Sort” menu item.

[spiros]

Of whole line. Many thanks, much indebted.

[spiros]

Thank you, I would appreciate it if you could. The specs is that it should be able to handle that specific file with 80 MB size, tab delimited with 10 columns, UTF-8 non-Latin text, and with line length ranging from 200 characters to 80,000.

[Author]

Posts