Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15127 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-10 14:04 -0400 |
| Last post | 2019-07-10 14:04 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: alias problem -- conflict found Chet Ramey <chet.ramey@case.edu> - 2019-07-10 14:04 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-10 14:04 -0400 |
| Subject | Re: alias problem -- conflict found |
| Message-ID | <mailman.861.1562781880.2688.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web