On 6/2/15 5:24 AM, Balaco Baco wrote:
> I'm surprised to read you saying that this is not a problem with Bash.
Because technically the history facilities are provided by readline, and
bash builds on those.
> I use Bash as my shell. As configure it (from its appropriate config
> file). And I get r
On 6/2/15 9:08 AM, Wheatley, Martin R wrote:
> $ echo $PATH
> /usr/bin:/usr/sbin:/usr/dt/bin:/home/USER/bin
> $
>
>
> a truss of "bash -ls" shows it stat'ing '-bash' in each of the directories
> in PATH...
>
> 11933: stat64("/usr/bin/-bash", 0xFFBFEBE8)Err#2 ENOENT
> 11933: stat64
On 6/2/15 11:37 AM, Greg Wooledge wrote:
> Ksh's nameref is completely different. With one of ksh's two different
> kinds of functions, you actually CAN use ksh nameref to pass a value
> back to the caller without variable name collisions.
In my opinion, the most interesting thing about ksh93's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/1/15 9:59 PM, Shawn Wilson wrote:
> Top posting as I'm kinda going out of band of the thread here;
>
> Having read the discussion, I guess the issue I brought up really
> isn't a "bug" (though Greg's points probably should be considered
> bugs).
On Tue, Jun 2, 2015 at 7:31 AM, Greg Wooledge wrote:
> There's declare -i, but no sane person USES that, so we can ignore it.
While in bash `-i` likely either has no effect or slows things down
very slightly, in ksh93 and probably zsh it's a huge performance win
because it prevents integers and f
