Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15836
| From | "Chris F.A. Johnson" <chris@cfajohnson.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Preventing Bash Variable Confusion |
| Date | 2020-01-29 09:37 -0500 |
| 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> |
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
Re: Preventing Bash Variable Confusion "Chris F.A. Johnson" <chris@cfajohnson.com> - 2020-01-29 09:37 -0500
csiph-web