Re: erc-element.el

[Emanuel Berg]

>> For non-interactive use, I vote no, because third-party
>> code may rely on that behavior, specifically those aspects
>> you find fault with. But what about applying this
>> exclusively to interactive invocations? That may still be
>> unwise because of the added complexity and possible
>> confusion arising from the disparity. But I suppose some
>> discussion regarding that would be warranted.
>
> For interactive use, they could be called from the button
> functions and placed in the same file [...]

It won't add complexity/confusion IMO, one would just add to
the docstring "For interactive use, the ERC prompt is
considered a button; also, cycling is in effect both ways."

-- 
underground experts united
https://dataswamp.org/~incal