Page 1 of 1

Let commands accept <crlf>-separated item lists

Posted: 08 Oct 2019 00:30
by highend
Some commands already do (it's autodetected if items are |- or <crlf> separated).
E.g. tagitems()
The help file states for these commands:
CRLF- or |-separated list of items (full path) to tag.
But most don't. E.g. delete. It would simplify the usage of all these commands if I don't need to
remember if it just accepts |-separated ones or not.

Why all the fuss? It's way easier to debug lists of "do something with me" when they
are <crlf> separated and I wouldn't need any conversions to feed them to commands
that only accept "|" ones. It would spare you from adding a separator= flag...

If you considering this, I'd compile a list of commands that would need this enhancement...

Re: Let commands accept <crlf>-separated item lists

Posted: 08 Oct 2019 09:35
by admin
Yes, please, a list would help.

Re: Let commands accept <crlf>-separated item lists

Posted: 29 Oct 2019 16:24
by highend
Commands that only support |-separated itemlists:

Code: Select all

attrstamp()
copyas, moveas
delete
hashlist
loadtree
moveto, copyto, backupto -> source parameter
openwith
rename
report()
selectitems
tag
timestamp
wipe

Re: Let commands accept <crlf>-separated item lists

Posted: 09 Nov 2019 16:13
by admin
Next beta will have it.

Re: Let commands accept <crlf>-separated item lists

Posted: 09 Nov 2019 20:03
by highend
Cool, thanks!