From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zach Riggle <zachriggle@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Weird expansion issue with (D)
Date: Fri, 12 Aug 2022 00:42:48 +0200 [thread overview]
Message-ID: <CAN=4vMpE3Z8PNR2b4m7ZVHSYtiVknoU8P0jmG1skNk8hmqtwkA@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5npEfDZOLoX=DcJLmZtM_nNHz-AodLfC2se7oFTa5Gm=A@mail.gmail.com>
On Fri, Aug 12, 2022 at 12:38 AM Zach Riggle <zachriggle@gmail.com> wrote:
>
> Is there any way to mark a specific variable name to NOT be expanded in this way?
Nope.
Are you sure you need auto_name_dirs? Perhaps you can use regular
named directories instead? If not, what's your use case that requires
auto_name_dirs?
Roman.
prev parent reply other threads:[~2022-08-11 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 16:36 Zach Riggle
2022-08-05 16:54 ` Roman Perepelitsa
2022-08-11 22:37 ` Zach Riggle
2022-08-11 22:38 ` Zach Riggle
2022-08-11 22:42 ` Roman Perepelitsa [this message]
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='CAN=4vMpE3Z8PNR2b4m7ZVHSYtiVknoU8P0jmG1skNk8hmqtwkA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=zachriggle@gmail.com \
--cc=zsh-users@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).