String

• search and match based on regex
• Add regex support for replace input
• Add function endwith a pattern

Arithmetic

• Add mod, pow, div and log etc. functions

Filesystem

• Add function mv to move and rename files
• More functions to filter files based on file mode bits and ownship

@leeleeee Sounds great. Especially the mv function, which will be really useful (we should add cp as well)

@sharkdp What do you think if we can add du or something like this?

@sharkdp What do you think if we can add du or something like this?

In which sense? Like a filesize :: Path -> Int function?

By the way, I just realized that the coreutils du commands works very nicely with functools:

> du | filter -c1 greater_than 8000 | map -c2 abspath
8340	/tmp/demo/folder/subdirectory
8408	/tmp/demo/folder
8480	/tmp/demo

Yeah, more precisely it is filesize :: Path -> String.

$ find . | map basename | filter startswith test_ | map filesize mb 
test_file1 1MB 
test_file2 5.2MB 

It is fantastic that linux commands are work very well with these functions. 👍

filesize is now supported.

• fst and snd for array-index access (alias for index 1 and index 2)
• replicate
• reverse

Does split currently work with variable size of whitespace between words? if not, does it make sense to add it? Something like below by default if no separator is provided, then it would be a nice replacement for awk

➜  ~ echo "a b         ccc " | ~/repos/shell-functools/ft/map split | map at 2
ccc

Does split currently work with variable size of whitespace between words?

It does not (yet). We could either provide a split_whitespace function which would simply call .split() without argument and/or provide a split_regex function which could be called with map split_regex '\s+'.

The reverse function, do you mean on array level, or on string level?

I think array-reverse can be useful. Not sure if we need a string-reverse function.

Hey @sharkdp, what about creating a max as well as min function in shell-functools? I can work on something if there is interest.

max :: Array -> Int
find . -name cnt.txt | xargs cat | max

@guilhermeleobas Sounds great!

These days, new unix/linux CLI tools are coming out supporting JSON outputs. Would it make sense to create a json function that can parse JSON outputs?

These days, new unix/linux CLI tools are coming out supporting JSON outputs. Would it make sense to create a json function that can parse JSON outputs?

I've been thinking about JSON support in the past, so this sounds interesting. What would this function do, exactly?

I can imagine there would a command named json which could be used like this:

$ curl http://echo.jsontest.com/key1/value1 | json key1

The curl command outputs {"key1": "value1"}. The whole command would output value1. The argument to json command would specify the path to the value you want. It could support the full json path spec or just a small part of it.

And then there would also a function called json which could be used like this:

$ curl <url that returns json in each line> | map json <json path>

In this case, the assumption is that the curl outputs a json-encoded string in each line, which is also a proposed standard format called jsonlines. And the map will transform each line with the json function.

$ <command that outputs json> | json <path to an array of objects> | map json <path in each object>

In the above command, the json command narrows data down to an array of objects, and then map json transforms each json into something. I think the path you specify could be some kind of template so that you can transform json into anything, which sounds a bit too ambitious.

Do you know jq? I think this could probably play well in combination with shell-functools.

@sharkdp jq seems to cover my use cases. Cool, thanks.

More functions that should be implemented:

• div/divide
• sum/product (working on arrays)
• matches => similar to starts_width/ends_with