voidtools forum

endwith: function requires a space (at least one) after the colon (:) (which is generally different from other functions, including startwith:).

endwith: appears to be working correctly here.

endwith:mp3 is showing files ending with mp3.
endwith: mp3 will match files with mp3 anywhere in the filename.

endwith: includes the extension.

Are you seeing something different?

Maybe the filename had an underscore (_){searchterm}.ext ?

Let me see if I can dig it up ...

File name: testing_256k.ext
I now realize that not all searches without the space fail, but some do.

And that is an underscore ( _ ) $5f$.
And some file name with underscores do work without needing the space.


File name: Avraam_Fried_Baal_shem_tov's_songs (directory name, actually)
But this fails, file name: Avraam_Fried_Baal_shem_tov's_songs.ext (a file in this instance, with the extension .ext)

Wait a minute, lol, sorry about that!
(And at some point I was going to request that, the ability to make the text in the help window bigger. Ah!)

Filenames (including extension) ending with text.

I was reading it as excluding, but its including.

Got it.
Sorry.

So maybe ...

help_box_font=
help_box_font_size=

I am considering going back to chm help files.

An option to scale just the help windows would be useful.

There is an option to scale all of the Everything UI elements in the Everything.ini called dpi
Try changing it to 128 or 144.

An option to change just the help text would be better though..

Adding another function, namepartendwith: would be useful for finding matches at the end of the name part.
endwith: only exists as an search optimization. endwith:.mp3 is the same as *.mp3 except it is much quicker.
If Match whole filenames when using wildcards is disabled, it also provides a mean to match the end of the filename, as *.mp3 would not necessary match the end of the filename.

I am considering going back to chm help files.

Never been a fan of that, compared to a simple text file that opens in a non-modal window.
chm, when maximized always seems to interfere with the underlying program. and its "bulky", to me at least, cause it is not simple text.

The "help" texts could even be in a simple text file, on disk, & just forward the wanted one on to (Horst's) ShowTx.
(Well, that's how I'd do it. Guess it might not be quite appropriate, assuming you could bundle his program with Everything.)

Edit: Thinking that really wouldn't be appropriate (even if I might happen to like it like that).

The current simple help text makes portability and localization easy and will likely stay.

I do wish to add more built-in help and chm files would be best for that.