2011-11-17, 13:38(-07), Eric Blake:
[...]
sed 's/^[[:blank:]]*\([^[:blank:]]*\)[[:blank:]]*()[[:blank:]]*{/ loca=
l FUNCNAME=3D\1;/'
Except that 'local' is not part of POSIX, so while this conversion may
work for dash, it's not a portable catch-all for other compliant shells.
[...]
Though
2014-10-08 15:26:36 +0800, Herbert Xu:
commit 3c06acdac0b1ba0e0acdda513a57ee6e31385dce
Author: Herbert Xu herb...@gondor.apana.org.au
Date: Wed Oct 8 15:24:23 2014 +0800
[EXPAND] Split unquoted $@/$* correctly when IFS is set but empty
Currently we do not field-split $@/$*
2014-11-10 21:20:02 +0800, Herbert Xu:
On Wed, Nov 05, 2014 at 11:59:47AM +, Stephane Chazelas wrote:
Hello,
ash/dash have a nice feature that allows to have:
PATH=/bin:%builtin:/usr/bin:/some/dir%func:/sbin
To have commands in /bin take precedence over builtins and
files
2014-11-10 22:59:38 +0100, Guido Berhoerster:
[...]
A much nicer solution would be to do something similar to the
original Korn shell and assign additional builtins a virtual
path which can be freely assigned in PATH and with which they can
be explicitly called. No more % in PATH and the
2014-11-10 23:39:51 +0100, Guido Berhoerster:
[...]
That leaves the /path%func
case but there is precendence with FPATH as a solution if % is
to be completely eliminated from PATH.
[...]
Where ash's $PATH handling is superior to $FPATH is that you can
specify which fpath component has
2014-11-11 14:23:21 +0100, Stephen Shirley:
[...]
[n1]n2Redirect standard output (or n1) to n2.
It doesn't cover the case where n2 is later changed, and how n1 does
not follow this, but it's the simplest fix i see.
[...]
That's ambiguous.
Maybe:
[n1]n2Redirect standard output (or
Hello.
[tested on current git head
f6d4def4e27b13fab174e948b94cd10550d3e10e]
Command substitution doesn't seem to work in $PS4 (used for
xtrace prompt):
$ PS4='$(date +%T) ' dash -xc :
dash: 1: Syntax error: end of file unexpected (expecting ))
And with the old syntax:
$ PS4='`date +%T` '
2014-12-08 22:22:03 +0100, Stéphane Aulery:
Le lundi 08 décembre 2014 à 08:37:38, Stephane CHAZELAS a écrit :
2014-12-08 19:50:05 +0100, Stéphane Aulery:
[n1]n2Redirect standard output (or fd n1) to the same open
file description as on fd n2.
[n1]n2Copy fd n2
2015-06-03 13:29:33 +0200, Martijn Dekker:
POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
${#parameter}
String Length. The length in characters of the value of parameter
shall be substituted. [...]
dash does not expand the length in
2015-12-03 23:17:58 +, Stephane Chazelas:
> 2015-12-03 23:04:31 +0000, Stephane Chazelas:
> [...]
> > > Summarising: POSIX states that "each occurrence in the input of an IFS
> > > character that is not IFS white space, along with any adjacent IFS white
>
2015-11-26 20:44:26 +0100, Gioele Barabucci:
> Hello,
>
> I am forwarding a bug [1] reported by a Debian user: dash incorrectly
> uses `$*` instead of the requested `$@` inside variable assignments.
> The current version of dash is affected by this bug.
>
> A simple test from the original
2016-02-11 15:30:59 +0100, Makarius:
[...]
> The problem is a deeper one, though: export -f in bash no longer
> works for systems that have /bin/sh -> dash (i.e. Debian and
> Ubuntu).
[...]
Note that pdksh/posh/mksh also strip those variables which it
can't map to shell variable names (and have
2016-09-07 11:55:00 -0400, Paul Smith:
> On Wed, 2016-09-07 at 16:44 +0200, Andrey Voropaev wrote:
> > if [ 0 -eq $UID ]
>
> The variable UID is not defined to be automatically set by the shell in
> POSIX; having it set is a bash extension. dash doesn't set it
> automatically for you.
>
>
13 matches
Mail list logo
