From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: activate alias inside subshell
Date: Sun, 8 Apr 2018 21:11:18 -0700 [thread overview]
Message-ID: <d3b98760-d70a-3ba0-1c1a-4cfb213906df@eastlink.ca> (raw)
In-Reply-To: <b02aae3b-967c-dee4-5275-91a61df3f282@eastlink.ca>
On 08/04/18 03:38 PM, Ray Andrews wrote:
>
>
> ... so it seems that I'm not going to get away with my previous
> anymore. Is there a new strategy that might work? Nullify the
> function and/or the alias? Really, just some way of stopping messages
> from printing at all?
>>
Heck it's easy, and no need for anything sick and twisted. Case closed.
Thanks for your patience Bart.
>>
>
>
prev parent reply other threads:[~2018-04-09 4:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 16:29 Ray Andrews
2018-04-07 19:57 ` Ray Andrews
2018-04-08 7:39 ` Bart Schaefer
2018-04-08 14:56 ` Ray Andrews
2018-04-08 20:18 ` Bart Schaefer
2018-04-08 20:54 ` Ray Andrews
2018-04-08 22:38 ` Ray Andrews
2018-04-09 4:11 ` Ray Andrews [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=d3b98760-d70a-3ba0-1c1a-4cfb213906df@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).