`waitfor` name conflicts with Windows built-in

[ErichDonGubler]

Just so you're aware: The name of this crate conflicts with Windows' built-in waitfor command.

[aeshirey]

Bummer. I had actually called this utility until, but then realized that it conflicts with the until keyword in bash. Happy to entertain suggestions for cross-platform uniqueness.

[ErichDonGubler]

Oooh, a brainstorming session. I can't resist. :) I'll try to avoid suggesting things that may already exist in cmd.exe, powershell.exe, bash, zsh....and, I suppose, fish too.

Ones to avoid

• sleep (built-in in POSIX shells)
• wait (built-in in POSIX shells)

Maybe-viable suggestions

• The idea behind the name itself isn't actually problem -- so, maybe changing the casing could be the Simplest™ way to resolve this particular issue (i.e., wait-for). Still not ideal in my head, since the edit distance from waitfor is tiny, but maybe you wouldn't consider that a problem.
• wtfr -- shortened version of waitfor, heh.
• after
• delay, delay-until, delayuntil
• wait-until, waituntil
• sleep-until, sleepuntil
• await -- I expected this to be a command name already taken, but I don't see it anywhere!

I could come up with more, if you want. 🤓

[aeshirey]

I'm not super concerned about the name at the moment, so I'm in no rush to change it. Maybe if this utility gets much more impressive than what it is now :)

That said, I prefer to follow the feel of GNU utils and have it be a single 'word' (such as waitfor versus something longer) or a short abbreviation (eg, wf). Another possibility is to have a different name for Windows in order to not conflict with the built-in.