Re: Keeping replace-buffer-contents runtime in bounds

[Eli Zaretskii]

> From: Tassilo Horn <address@hidden>
> Cc: address@hidden
> Date: Sun, 17 Feb 2019 19:26:04 +0100
> 
> > Thanks for working on this.  My only other comment is that maybe we
> > should allow passing the time-out value via the function's arguments,
> > not via a global variable.  It seems to me the time-out will be used
> > in more use cases than MAX-COSTS, and in any case treating these two
> > differently API-wise sounds strangely inconsistent.
> 
> I'll do that.  So two optional args and MAX-SECS as the first one,
> right?

Yes, that's what I had in mind.

Thanks.