> What does `(c)uts` tell you?
Cut points (by \n, in this case) if one were to use the cut operator _ to tokenize a by leading \n.
It's hint/reminder of the purpose of the definition.
N.B. - This feature (i.e. str$chr) is undocumented in k.txt. I would normally use &a="\n".
However, as soon as I saw Arthur's comment, it made sense (and uses less memory).
> We know the types of the data when we're tracing the code path.
My goal is to avoid having to trace the code path and to understand the definition in isolation (or as isolated as possible).
E.g. - you were able to add HOME/END functionality for your Mac without understanding the entire code path.
> d::(#c),|/-':b::0,1+c::a$"\n"
> You should let Arthur know.
Will do. He definitely appreciates concision.
Btw, I'm using k5 for daily use. Are you? If so, we could share notes.
It's hint/reminder of the purpose of the definition.
N.B. - This feature (i.e. str$chr) is undocumented in k.txt. I would normally use &a="\n". However, as soon as I saw Arthur's comment, it made sense (and uses less memory).
> We know the types of the data when we're tracing the code path.
My goal is to avoid having to trace the code path and to understand the definition in isolation (or as isolated as possible).
E.g. - you were able to add HOME/END functionality for your Mac without understanding the entire code path.
> d::(#c),|/-':b::0,1+c::a$"\n"
> You should let Arthur know.
Will do. He definitely appreciates concision.
Btw, I'm using k5 for daily use. Are you? If so, we could share notes.