From: Bart Schaefer <schaefer@brasslantern.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
Glyph <glyph@twistedmatrix.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: bug report: INTERACTIVECOMMENTS option interacts oddly with shell functions in an interactive context
Date: Tue, 31 Aug 2021 20:41:57 -0700 [thread overview]
Message-ID: <CAH+w=7Z8rhQA_N_Ui+YQezDSWAa4Ro_4fsrNdjz6ZCz+SE3cKQ@mail.gmail.com> (raw)
In-Reply-To: <20210831060354.srascacw2zk35cnm@chazelas.org>
On Mon, Aug 30, 2021 at 11:03 PM Stephane Chazelas
<stephane@chazelas.org> 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 $(...).
next prev parent reply other threads:[~2021-09-01 3:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 20:55 Glyph
2021-08-30 21:35 ` Bart Schaefer
2021-08-31 6:03 ` Stephane Chazelas
2021-09-01 3:41 ` Bart Schaefer [this message]
2021-09-01 7:55 ` Stephane Chazelas
2021-09-01 15:17 ` Peter Stephenson
2021-09-01 17:55 ` Bart Schaefer
2021-09-01 18:09 ` Bart Schaefer
2021-09-01 18:23 ` Stephane Chazelas
2021-09-01 18:41 ` Stephane Chazelas
2021-09-01 18:43 ` Bart Schaefer
2021-09-02 9:04 ` Peter Stephenson
2021-09-09 3:50 ` Bart Schaefer
2021-09-09 19:06 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7Z8rhQA_N_Ui+YQezDSWAa4Ro_4fsrNdjz6ZCz+SE3cKQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=glyph@twistedmatrix.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).