News for hackers. Stuff that matters.
Re:Debounce in Bash by cryptonector on Monday September 24, 2018 @07:14PM (#18062301)
When measuring elapsed times, instead of executing date(1) to get the current time, use $SECONDS:

       SECONDS
              Each time this parameter is referenced, the
              number of seconds since shell invocation
              is returned.  If  a  value  is  assigned
              to  SECONDS,  the  value returned  upon
              subsequent references is the number of
              seconds since the assignment plus the
              value assigned.  If SECONDS is unset, it
              loses its special properties, even if it is
              subsequently reset.
Like so:

  throttle() {
    local -i limit
    ((limit = SECONDS + $1))
    while read line; do
      if ((limit < SECONDS)); then
        ((limit = SECONDS + $1))
        echo "$line"
      fi
    done
  }
Try it like so:

  $ yes | throttle 2
Of course, that's a bad example in that yes(1) will go as fast as you let it and it always outputs the same thing. In the case of yes(1) the better thing to do would be to sleep between reads, but yes(1) is a special case.
Re:Debounce in Bash by anothergoogler on Monday September 24, 2018 @07:50PM (#18062479)
It's worth noting that OP's example works in any Bourne-compatible shell. I don't think `date +%s` is costly enough to warrant losing the portability.
Re:Debounce in Bash by kadoban on Tuesday September 25, 2018 @12:28AM (#18063604)
I wouldn't be worried about the performance cost of using `date +%s` personally, I'd be concerned about what happens when the user or an automated process changes the system time.

For example, what will happen in the debounce function if the user sets the system time backwards by a week after a limit has been set?

Re:Debounce in Bash by anothergoogler on Tuesday September 25, 2018 @01:16AM (#18063786)
Good point, didn't think of that.
Re:Debounce in Bash by cryptonector on Tuesday September 25, 2018 @12:16PM (#18067665)
The title said bash.

Replace "local" with "typeset" and what I wrote is compatible with KSH too -- not Bourne nor POSIX, I know, but still.