Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail From: Linda Walsh Newsgroups: gnu.bash.bug Subject: Re: updating shopt compat settings to include current version Date: Thu, 15 Oct 2015 11:01:48 -0700 Lines: 23 Approved: bug-bash@gnu.org Message-ID: References: <20151015173433.GS4446@vapier.lan> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1444932207 27886 208.118.235.17 (15 Oct 2015 18:03:27 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org User-Agent: Thunderbird In-Reply-To: <20151015173433.GS4446@vapier.lan> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 173.164.175.65 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11664 Mike Frysinger wrote: > with bash-4.0, new compat options were introduced: > shopt -s compat32 > and with bash-4.3, a variable was added: > export BASH_COMPAT=3.2 ---- > shopt -p|grep compat43 > # (no output) --- Maybe if you could check if there is a compat setting for a given version, since compat's aren't usually defined until the following version --- and THEN, only if 4.4 changed something that it needed a compat43 option. AFAIK, compats were introduced because of newer versions being incompat in some way to the old. But if there is no incompat, there wouldn't be a need for a compat43 option... Else shopt's options will just grow/grow/grow..... ??