Allow emoji's used by a command to be defined by the user

[plastikfan]

standardise emoji usage, by assigning specific emojis to well defined actions, so this can be made to be uniform accross multiple commands

[plastikfan]

SIGNALS:

• file rename clash
• true assertion/flag ('✔️')
• file indicator a/b
• directory indicator a/b
• cut operation a/b
• copy operation a/b
• move operation a/b
• paste operation a/b
• pattern
• literal
• crumb a/b
• overwrite a/b
• whatif
• failed a/b
• skipped a/b
• audio
• text
• document
• image
• movie
• summary a/b
• ok a/b
• bad a/b

rename-many

• anchor

[plastikfan]

The default signal/emoji list needs to be defined for each platform;

[environment]::OSVersion.Platform

[plastikfan]

I discovered why for files the indentation was out by 1. It was very obscure. The icon being used to represent a file was the label emoji:

🏷️

For some reason, presumably, it was using one more space than other emojis, since the indent value of 39, used for directories had to be modified to 40 for files. This seemed to make no sense and still doesnt. The only way round this for now is to avoid the label emoji until it's found out what's different about this one (and I suppose potentially there are other emojis which are likewise afflicted).

Actually, we can see the problem as follows:

$sigs = Get-Signals
$sigs['FILE-A'][1]   # => 🏷️
($sigs['FILE-A'][1]).Length # => returns 3 !!!!!
($sigs['FILE-B'][1]).Length # => returns 2 as expected

So some emojis are length 3 and not the normal 2.