From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Can an alias ever have a dynamic element?
Date: Tue, 17 Dec 2013 09:15:56 -0800 [thread overview]
Message-ID: <131217091556.ZM8432@torch.brasslantern.com> (raw)
In-Reply-To: <XnsA2999C087BB98davidrayninfocouk@80.91.229.13>
On Dec 17, 3:20pm, zzapper wrote:
}
} I have an alias which creates a tar with a date component in its name
} that date is however evaluated when the shell is created which could
} have been a few days ago. The easy solution is to create a script but
} is they any alternative?
This usually means you've created the alias with something like:
alias thingy="foo $(date)"
when what you need are single rather than double quotes:
alias thingy='foo $(date)'
Always best if you actually show us an example rather than attempt to
describe it in prose.
next prev parent reply other threads:[~2013-12-17 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 15:20 zzapper
2013-12-17 16:04 ` Phil Pennock
2013-12-17 17:15 ` Bart Schaefer [this message]
2013-12-17 18:41 ` zzapper
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=131217091556.ZM8432@torch.brasslantern.com \
--to=schaefer@brasslantern.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).