Re: Preventing Bash Variable Confusion

Path	csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From	"Chris F.A. Johnson" <chris@cfajohnson.com>
Newsgroups	gnu.bash.bug
Subject	Re: Preventing Bash Variable Confusion
Date	Wed, 29 Jan 2020 09:37:23 -0500 (EST)
Lines	13
Approved	bug-bash@gnu.org
Message-ID	<mailman.29.1580308669.2384.bug-bash@gnu.org> (permalink)
References	<20200128210225.GC12574@localhost4.local> <20806.1580277461@jinx.noi.kre.to> <20200129142305.GX1350@eeg.ccf.org> <alpine.DEB.2.21.2001290936280.27533@chris>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset=US-ASCII; format=flowed
X-Trace	usenet.stanford.edu 1580308670 11161 209.51.188.17 (29 Jan 2020 14:37:50 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	bug-bash@gnu.org
To	Greg Wooledge <wooledg@eeg.ccf.org>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m2o5g0.a1-4.dyn; x=1580309566; h=Feedback-ID: X-Smtpcorp-Track:Message-ID:Subject:To:From:Date:Reply-To:Sender: List-Unsubscribe; bh=mGOBMb/ABgLHVkSHBpaqAalLzc2Am/uhTCLl2c8hjxc=; b=PFTnWi/q c7qnalXOGOuZiYadN0G5kNcJjtG5BK7BXp/OEPSyBWYS9BOBG0Z0M1GyLIi97NK70Srk/nTNBx7lU vEOcUbHuk/6PkGEYvSzIgKQaPyczqrz+jeQLsQguKYicYp/czgOzVMiI4JwClh2vyentkO/BEVBaY lTJylRLeKmAHXMeBS49USvk3lz2eo6bO95uXsB2qKLnF7Dhg9nPdMSwCBrKYH8YHAyP5sV5HVYDfK jBO9e1ch2xLo/IHyS3uySXPUwpmjO+djrnBm8FN2AMIwTi3GQ9lm4meMwSuHsAp/eWYj2yDmkhjEy PBj7AE8Cdv6EWD01eo3eEFD9hQ==;
X-X-Sender	chris@chris
In-Reply-To	<20200129142305.GX1350@eeg.ccf.org>
User-Agent	Alpine 2.21 (DEB 202 2017-01-01)
X-Smtpcorp-Track	1iwoTE095GIImK.udiIxekqa
Feedback-ID	124612m:124612a-vpTX9:124612sMncmGVQT5
X-Report-Abuse	Please forward a copy of this message, including all headers, to <abuse-report@smtp2go.com>
X-detected-operating-system	by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From	103.47.205.39
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.23
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<https://lists.gnu.org/archive/html/bug-bash>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID	<alpine.DEB.2.21.2001290936280.27533@chris>
X-Mailman-Original-References	<20200128210225.GC12574@localhost4.local> <20806.1580277461@jinx.noi.kre.to> <20200129142305.GX1350@eeg.ccf.org>
Xref	csiph.com gnu.bash.bug:15836

Show key headers only | View raw

On Wed, 29 Jan 2020, Greg Wooledge wrote:

> As long as you use at least one lowercase letter in your variable name,
> you are guaranteed not to conflict with any internal shell variables.

    Except for auto_resume and histchars.

-- 
    Chris F.A. Johnson                         <http://cfajohnson.com/>
    =========================== Author: ===============================
    Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
    Pro Bash Programming: Scripting the GNU/Linux shell (2009, Apress)

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

Thread

Re: Preventing Bash Variable Confusion "Chris F.A. Johnson" <chris@cfajohnson.com> - 2020-01-29 09:37 -0500

csiph-web