XYplorer Beta Club

Sorry: isn't this a bit ineffective?

Instead of creating a function trim(string, character=" ", position=both) allowing the above functionality by
trim(gettoken(string, index, separator))
and adding many more abilities, together with gettoken as well as many other types of usage, (for example with foreach, with getkey, and others,) you restrict this trim to only be used with/inside gettoken, and to only strip spaces left and right.

I'm a bit puzzled.

Relax, I added trim(). Just forgot to add it to the change log.

admin wrote:Relax, I added trim(). Just forgot to add it to the change log.

Code: Select all

text trim("  d  ");

This man ...

No complaint, just a question: if I guess it right it only can trim spaces?
(As I see no operand to specify the character to trim )

Yes, not yet.

admin wrote:Yes, not yet.

If, somewhen, you might expand it, I would remind you of a possible 3rd operand leading, trailing, or both, with both as default.

But I wouldn't be surprised, if you did it allready

PeterH wrote:

admin wrote:Yes, not yet.

If, somewhen, you might expand it, I would remind you of a possible 3rd operand leading, trailing, or both, with both as default.

But I wouldn't be surprised, if you did it allready

Not yet, but I like it. ... Now I did it.

Oh well ... in that case how about a special settings for whitespace characters horizontal (tab space) and vertical (tab CR LF FF NEL).

admin wrote:Not yet, but I like it. ... Now I did it.

http://www.xyplorer.com/xyfc/viewtopic. ... 450#p71450

But why with numbers 1,2,3 as mode parameter? Why not simple L,R,B instead (or best additionally)?

I see usefulness on this if i could trim a string:

a. from a given string onwards or backwards up to the end or down to the start of its original line (or both)

b. same as above but up to a certain limit of characters

c. same as 'b' but able to state wildcards or explicit charlists as limits

d. inserting a replacement for the trimmed strings

more of a blind erasing function instead of trimming known characters.

neutrox wrote:I see usefulness on this if i could trim a string:

a. from a given string onwards or backwards up to the end or down to the start of its original line (or both)

b. same as above but up to a certain limit of characters

c. same as 'b' but able to state wildcards or explicit charlists as limits

d. inserting a replacement for the trimmed strings

more of a blind erasing function instead of trimming known characters.

You talk about trim()?

d. says you talk about replace()
and the very last line says you talk about erase()

Sure - they could be helpful, too.

But you say the current trim is not useful?
Strange...

@Don: quite some function in it that I didn't expect
(Especially the generic versions...)
I need (some time) to digest that.

But thanks: it surely will be helpful, at least for me!

I replaced the numbers by letters, but anything more appears overkill or simply "untrimmish".

Is there a way to trim the last 4 characters off the file name strings? Folderreport returns filenames as strings and I want to cut off the period/extension from the end of the string. All I want is the file name base as a string.

Trim() isn't what you're looking for.

If you really only have the file name there is to do this...

Otherwise (with full path) use:

Thank you thank you. The second code worked perfectly. It would have been a pain for me to figure out all those little switches.