Subject: Re: bug#15443: hs-forward-sexp design issue

From: Lars Ingebrigtsen <[email-masked]>
Date: Sat, 26 Dec 2015 01:59:51 +0100

Andreas Röhler <[email-masked]> writes:

> hs-forward-sexp insists to be called with an argument
>
>     (funcall hs-forward-sexp-func arg)))
>
> That way it's not possible to instrument hs-forward-sexp-func just saying
>
> (search-forward "something")
>
> Instead
>
> (lambda (arg)(search-forward "something"))
>
> would be required.
>
> As it's a function to be set by modes/users
>
> life will be easier if this argument is optional.

The argument has to be a function -- it can't just be a form.  That
would be very odd.  So I don't think there's anything to do here, and
I'm closing the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no