Re: bug report: INTERACTIVECOMMENTS option interacts oddly with shell functions in an interactive context

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Mon, Aug 30, 2021 at 11:03 PM Stephane Chazelas
<stephane@xxxxxxxxxxxx> wrote:
>
> But that used to work OK, up to 5.4.1 at least, and also applies
> to echo $(#comment) outside of functions.

+Changes from 5.4 to 5.4.3
+-------------------------
+
+The effect of the NO_INTERACTIVE_COMMENTS option extends into $(...) and
+`...` command substitutions when used on the command line.  Previously,
+comments were always recognized within command substitutions unless the
+comment character "#" was disabled via reset of $histchars.

Thread started with workers/41656 (September 2017) about writing
aliases that start with "#" and being able to use them inside $(...).