Re: alias problem -- conflict found

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: alias problem -- conflict found
Date	2019-07-10 14:04 -0400
Message-ID	<mailman.861.1562781880.2688.bug-bash@gnu.org> (permalink)
References	(3 earlier) <20190709132112.GW2450@eeg.ccf.org> <10340.1562742284@jinx.noi.kre.to> <11760.1562772554@jinx.noi.kre.to> <5D260BD8.8010800@tlinx.org> <480d3363-dce0-6629-b1f6-bca0b006cc88@case.edu>

Show all headers | View raw

On 7/10/19 12:01 PM, L A Walsh wrote:

> What do you think aliases are?  They are both a simple hash substitution.

They might appear superficially similar, and they use similar internal
abstractions.

> declare -A BASH_CMDS=([ls]="/usr/bin/ls" )
> declare -A BASH_ALIASES=([ls]="/bin/ls" )

And I made them both available using array syntax, using a different
internal mechanism, but:

> Aliases are store/implemented using hashes the same as stored paths
> are.  They are effectively the same.

Which is not at all what you said initially.

This isn't ksh, using `tracked aliases' to expose hashed pathnames.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: alias problem -- conflict found Chet Ramey <chet.ramey@case.edu> - 2019-07-10 14:04 -0400

csiph-web