Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: continued alias problem -- some work, some don't, why? Date: Tue, 9 Jul 2019 09:21:12 -0400 Lines: 31 Approved: bug-bash@gnu.org Message-ID: References: <5D23C417.5060108@tlinx.org> <20190709132112.GW2450@eeg.ccf.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1562678498 26933 209.51.188.17 (9 Jul 2019 13:21:38 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org Mail-Followup-To: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: <5D23C417.5060108@tlinx.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20190709132112.GW2450@eeg.ccf.org> X-Mailman-Original-References: <5D23C417.5060108@tlinx.org> Xref: csiph.com gnu.bash.bug:15095 On Mon, Jul 08, 2019 at 03:30:47PM -0700, L A Walsh wrote: > alias my='declare ' > alias Export='-x ' > alias Map='-A ' > alias Int='-i ' > > my Export Map Int ffffe=([one]=1) > -bash: declare: `-x': not a valid identifier > -bash: declare: `-A': not a valid identifier > -bash: declare: `-i': not a valid identifier This is what I get when I run your commands: wooledg:~$ alias my='declare ' wooledg:~$ alias Export='-x ' wooledg:~$ alias Map='-A ' wooledg:~$ alias Int='-i ' wooledg:~$ my Export Map Int ffffe=([one]=1) wooledg:~$ set | grep -e Export -e Map -e Int -e ffffe _=ffffe ffffe=([one]="1" ) wooledg:~$ declare -p ffffe declare -Aix ffffe=([one]="1" ) Because the dead horse is still equine-shaped, I will beat upon it some more: this is utterly horrible coding and you should stop doing it. I strongly disagree with your decision to do this, but whatever bug you're seeing, I'm not seeing it. Not in bash 5.0 or 4.4, anyway, which are the only two versions I tried.