skalibs and related 2.0
For those of us who use (and don't mind) slashpackage conventions for our non-packaged code, what changes are we going to need once the new s6 stuff lands? Based on prior comments I'm assuming it'll still be a viable option, but it'd be nice to know ahead of update day. Cheers! -- "If the doors of perception were cleansed every thing would appear to man as it is, infinite. For man has closed himself up, till he sees all things thru' narrow chinks of his cavern." -- William Blake
Re: execline: accessing LASTEXITCODE environment variable
On Wed, 20 Aug 2014 08:25:30 +0100 Laurent Bercot wrote: > > This is contrary to the documentation, but it appears to set > > the environment variable '?', not LASTEXITCODE: > > Ah, I'm sorry, I forgot to update the foreground documentation. My bad. > > Starting with execline-1.3.0, LASTEXITCODE has been changed to ? > and LASTPID to ! ; and the pipeline utility also sets ! . > Documentation now updated. > > You can get the old behaviour by compiling with -DEXECLINE_OLD_VARNAMES, > but please do not rely on this for too long. (execline-2.0 is just around > the corner, and I may or may not remove support for old variables.) > > -- > Laurent Ah, good deal. Thank you, Patrick and Laurent, for clearing this up. $? is same as shell, so makes the transition that much easier. John
Re: execline: accessing LASTEXITCODE environment variable
This is contrary to the documentation, but it appears to set the environment variable '?', not LASTEXITCODE: Ah, I'm sorry, I forgot to update the foreground documentation. My bad. Starting with execline-1.3.0, LASTEXITCODE has been changed to ? and LASTPID to ! ; and the pipeline utility also sets ! . Documentation now updated. You can get the old behaviour by compiling with -DEXECLINE_OLD_VARNAMES, but please do not rely on this for too long. (execline-2.0 is just around the corner, and I may or may not remove support for old variables.) -- Laurent
