Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15855 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2020-01-30 08:35 -0500 |
| Last post | 2020-01-30 08:35 -0500 |
| 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: Preventing Bash Variable Confusion Greg Wooledge <wooledg@eeg.ccf.org> - 2020-01-30 08:35 -0500
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-01-30 08:35 -0500 |
| Subject | Re: Preventing Bash Variable Confusion |
| Message-ID | <mailman.102.1580391358.2384.bug-bash@gnu.org> |
On Thu, Jan 30, 2020 at 11:37:26AM +0800, konsolebox wrote: > You can still use all caps on global variables just mind the internal > variables. Easier said than done. How many times have you had to diagnose someone's failing script, and it turned out the reason it was failing was because they used a variable like HOME or PATH or USER and "forgot" that it would conflict with a special/environment variable? For me, that answer is "too many".
Back to top | Article view | gnu.bash.bug
csiph-web