Re: Comment (# char) behavior in the sub-shell

[Stanislav Seletskiy <s.seletskiy@xxxxxxxxx>]

> (Paranoia.)
> 
> I see, however, "nocomments" isn't saved and restored as we enter
> different levels of reading history, which could be a problem.  But I
> don't think so --- you're just modifying around *parsing* a string, not
> execution of the result, so there's no possibility of the effect being
> passed on where it shouldn't be.
> 
> Is there?
> 
> [The sombre background music to this post is available at all online
> retailers.]

I'm using your patch and it works great.

Is there chance it will be merged into upstream? I really miss that
functionality.