Re: Only one Friday 13th coming in 2016

2015-12-23 Thread Bill Duncan
Dang! I love this list. Looks like I haven't done a "man cal" for many years. I didn't know about "ncal".. lol. I remember there was a note in the old Version 7 manuals about reading the man pages periodically.. Thanks Ken! On Tue, Dec 22, 2015 at 10:59:18AM -0900, Ken Irving wrote: > On Tu

Re: Strange Problem with 'test' or '['

2015-12-23 Thread Greg Wooledge
On Wed, Dec 23, 2015 at 04:05:28PM +0100, Bytec GmbH - Helmut Koeberle wrote: > OK, with '[[' ist's working! > > if ([[ "true" = "true" ]] && [[ "${h:0:1}" = "/" ]]); then echo slash; fi You don't need parentheses around it. The parentheses force the commands to run in a subshell (fork()), so it

Re: Feature discussion - startup files

2015-12-23 Thread Chet Ramey
On 12/21/15 6:17 PM, Ángel González wrote: > Chet Ramey wrote: >> The current configurable startup file options are insufficient for >> their purposes because they can be enabled or disabled by vendors, >> and these folks would rather not modify the "vendor" parts of the >> system. In some cases, w

Re: Feature discussion - startup files

2015-12-23 Thread Chet Ramey
On 12/21/15 11:11 PM, Rob Foehl wrote: > Further, the "do it, regardless" aspect of this proposal is particularly > worrisome: the last thing anyone needs is another unconditionally sourced > system-wide file in the style of bash_logout. No more, please. Ironically, the system-wide bash_logout f

Re: Feature discussion - startup files

2015-12-23 Thread Chet Ramey
On 12/23/15 8:05 AM, Greg Wooledge wrote: > tl;dr: I won't complain if Chet makes this a compile-time option, but > I would prefer that it default to "not enabled". I semi-offered this, but it's not sufficient: the request is for something that is not optional, enabled by default, not configurabl

Re: Strange Problem with 'test' or '['

2015-12-23 Thread Chet Ramey
On 12/23/15 5:26 AM, Bytec GmbH - Helmut Koeberle wrote: > Hello list, > > i have a strange problem in bash with the test command. > > Here is my simple bash script 'tst' that checks wether the first char of > an argument is a slash. > If the first char of the argument is a special char like '('

Re: Feature discussion - startup files

2015-12-23 Thread Piotr Grzybowski
On Wed, Dec 23, 2015 at 2:05 PM, Greg Wooledge wrote: > [..] > On the one hand, we have draconian control-freak admins who want to > impose their policy on every user unconditionally, through things > like /etc/bash.bashrc (or /etc/bashrc or however the vendor chooses > to spell it). And now appa

Re: Strange Problem with 'test' or '['

2015-12-23 Thread Greg Wooledge
On Wed, Dec 23, 2015 at 11:26:51AM +0100, Bytec GmbH - Helmut Koeberle wrote: > Here is my simple bash script 'tst' that checks wether the first char of > an argument is a slash. It can be written in a much simpler way: [[ $arg = /* ]] Or: case $arg in /*) ... This part actually does look like

Re: Feature discussion - startup files

2015-12-23 Thread Chet Ramey
On 12/23/15 8:48 AM, Fotis Georgatos wrote: > Interestingly, I find kinda control-freak the approach of not permitting a > *voluntarily* usable feature, > which is a pretty much a standard facility across many other shells. Please, let's not get carried away here. zsh is the only Bourne-style s

Re: Feature discussion - startup files

2015-12-23 Thread Chet Ramey
On 12/23/15 2:49 AM, Rob Foehl wrote: > On Tue, 22 Dec 2015, Fotis Georgatos wrote: > >> Compare bash vs zsh: >> http://blog.flowblok.id.au/static/images/shell-startup-actual.png Please stop referring to this diagram; it is misleading in that it assumes that a large number of things that are off

Strange Problem with 'test' or '['

2015-12-23 Thread Bytec GmbH - Helmut Koeberle
Hello list, i have a strange problem in bash with the test command. Here is my simple bash script 'tst' that checks wether the first char of an argument is a slash. If the first char of the argument is a special char like '(' then it works if there is one expression, but not with multiple express

Re: Feature discussion - startup files

2015-12-23 Thread Fotis Georgatos
Hi Greg, The mere existence of -and ability to manage-, say, /etc/zshenv does not enforce any particular policy on a given system, it simply allows for the possibility to have a single control point for all shell instances. Unfortunately, a compile time option for bash, is not a feature at the sa

Re: bug: readonly array that is empty causes error (whereas not empty does not)

2015-12-23 Thread Chet Ramey
On 12/23/15 1:49 AM, James Thomas Moon wrote: > The following script is okay > > set -ue > readonly -a a=('') > > Yet, the following script fails with exit code 1 > > set -ue > readonly -a a=() > > In my case, I would like to preserve a copy of all passed arguments: > > set

Re: bug: readonly array that is empty causes error (whereas not empty does not)

2015-12-23 Thread Piotr Grzybowski
On Wed, Dec 23, 2015 at 12:29 PM, konsolebox wrote: > On Wed, Dec 23, 2015 at 2:49 PM, James Thomas Moon wrote: >> In my case, I would like to preserve a copy of all passed arguments: [..] > I can't reproduce this. My script always returns 0. same here. cant reproduce on any version. pg

Re: Feature discussion - startup files

2015-12-23 Thread Greg Wooledge
On Mon, Dec 21, 2015 at 03:19:46PM -0500, Chet Ramey wrote: > I've been approached by some HPC system administrators (who have the > unenviable task of supporting thousands of users) who have requested a > new feature in bash: a system startup file with a fixed name (e.g., > /etc/bashenv) that is s

Re: Command-line char insertion segfault

2015-12-23 Thread konsolebox
On Wed, Dec 23, 2015 at 3:07 AM, Carlo Milanesi wrote: > On 12/22/2015 03:38 PM, Chet Ramey wrote: >> >> On 12/21/15 7:38 PM, Carlo Milanesi wrote: >> >>> Bash Version: 4.3 >>> Patch Level: 11 >>> Release Status: release >>> >>> Description: >>> Every time I insert a character in a command-li

Re: bug: readonly array that is empty causes error (whereas not empty does not)

2015-12-23 Thread konsolebox
On Wed, Dec 23, 2015 at 2:49 PM, James Thomas Moon wrote: > In my case, I would like to preserve a copy of all passed arguments: > > set -ue > readonly -a ARGS=("${@}") > > If no arguments are passed then the script fails. It's surprising the error > behavior diverges depending upon setti

[patch] store local port after successful connection via network redirections (/dev/{tcp,udp}/host/port)

2015-12-23 Thread Piotr Grzybowski
Hi. I have had a need to know the number of the client port after successful exec 4<>/dev/tcp/${host}/${port} [..] The attached patch stores the local, client port in the variable LOCALPORT. Would you accept this new feature? We need it due to specific on-site security considerations. There

Re: Command-line char insertion segfault

2015-12-23 Thread Piotr Grzybowski
Hi Carlo, On Wed, Dec 23, 2015 at 12:44 AM, Carlo Milanesi wrote: > On 12/22/2015 09:14 PM, Piotr Grzybowski wrote: >> >> [..] Whats your locale? > > > I originally set partially it_IT locales, and partially en_US locales, then > changed all to en_US, but I still have an Italian keyboard. > The o

Include column in syntax error message

2015-12-23 Thread Karl-Philipp Richter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Currently, syntax error messages like ``bash: syntax error near unexpected token `;'``, e.g. after issuing `echo a &; echo b &; echo c &;` aren't as helpful as they could be. It'd be nice to know at which column, i.e. which `;`, the message refer

bug: readonly array that is empty causes error (whereas not empty does not)

2015-12-23 Thread James Thomas Moon
The following script is okay set -ue readonly -a a=('') Yet, the following script fails with exit code 1 set -ue readonly -a a=() In my case, I would like to preserve a copy of all passed arguments: set -ue readonly -a ARGS=("${@}") If no arguments are passed then the