>what is stopping from interpreting 1h in similar manner to 3600? i.e. from now
No, this is user-friendly, and thus can't be done :) But if think a second, sleep is used rarely by average users, mostly by programmers and other scripts, and they should know better what they are doing. Seriously, that explanation about different hours is not enough to prevent at least useful option. like sleep -f 1h (-f means force convert, without it you can see good explanation why sleep for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at all.). Exact units in which sleeps happens (seconds, ticks, minutes, years) can be described in manual page, even without accepting m,h - that info would be useful for one. P.S. There is already non-portable feature in sleep - non-integer, and I'm sure that no one thought about some financists from various countries, who used to specify long numbers with separator, e.g. 3.600, and this means for them one hour and not 3 point 6 seconds. -- Regards, Alexander Yerenkow _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
