[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: alias problem -- conflict found
From: |
Greg Wooledge |
Subject: |
Re: alias problem -- conflict found |
Date: |
Wed, 10 Jul 2019 11:54:27 -0400 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Wed, Jul 10, 2019 at 10:29:14PM +0700, Robert Elz wrote:
> From: L A Walsh <bash@tlinx.org>
> | Functions can't process their arguments in the current scope.
>
> I have no idea what you're getting at there.
She wants something like Tcl's [uplevel] command, most likely.
http://www.tcl.tk/man/tcl8.6/TclCmd/uplevel.htm
Short version: evaluate a command in the caller's scope, instead of in
the function's scope. In Tcl, you can use this (WITH EXTREME CAUTION)
to implement new commands with the semantic powers of "if" or "for".
It makes "eval" look like a toy.
Bash has nothing like this. Bash doesn't even come CLOSE to this.
It was never designed for this. It's a SHELL. If she's using aliases
to try to mimic this behavior, I have nothing more to say on this topic.
Horse, beating.
Re: alias problem -- conflict found, Robert Elz, 2019/07/10
Re: alias problem -- conflict found, Robert Elz, 2019/07/10
Re: alias problem -- conflict found,
Greg Wooledge <=
Re: alias problem -- conflict found, L A Walsh, 2019/07/10
Re: alias problem -- conflict found, Chet Ramey, 2019/07/10
Re: alias problem -- conflict found, L A Walsh, 2019/07/10
Re: alias problem -- conflict found, Eli Schwartz, 2019/07/10
Re: alias problem -- conflict found, Robert Elz, 2019/07/11
Re: alias problem -- conflict found, Chet Ramey, 2019/07/11
Re: alias problem -- conflict found, L A Walsh, 2019/07/12
Re: alias problem -- conflict found, Eli Schwartz, 2019/07/12
Re: alias problem -- conflict found, L A Walsh, 2019/07/12
Re: alias problem -- conflict found, Dennis Williamson, 2019/07/12