btw in the help you pasted there is the -a arr in question
On Mon, Sep 6, 2021, 08:36 felix wrote:
> On Sun, Sep 05, 2021 at 11:54:05PM -0400, Lawrence Velázquez wrote:
> > On Sun, Sep 5, 2021, at 11:11 PM, Dale R. Worley wrote:
>
> > > > ... I was wondering, is there a way for bash to know wher
i totally agree with any make subshells obsolete ( for cpu speed ) plans
On Mon, Sep 6, 2021, 08:36 felix wrote:
> On Sun, Sep 05, 2021 at 11:54:05PM -0400, Lawrence Velázquez wrote:
> > On Sun, Sep 5, 2021, at 11:11 PM, Dale R. Worley wrote:
>
> > > > ... I was wondering, is there a way for bas
On Sun, Sep 05, 2021 at 11:54:05PM -0400, Lawrence Velázquez wrote:
> On Sun, Sep 5, 2021, at 11:11 PM, Dale R. Worley wrote:
> > > ... I was wondering, is there a way for bash to know where the
> > > symlink points (without using an external program)?
>
> The distribution ships with a "realpath
On Sun, Sep 5, 2021, at 11:11 PM, Dale R. Worley wrote:
> L A Walsh writes:
> > I know how -h can detect a symlink, but I was wondering, is
> > there a way for bash to know where the symlink points (without
> > using an external program)?
>
> My understanding is that it has been convention to use
L A Walsh writes:
> I know how -h can detect a symlink, but I was wondering, is
> there a way for bash to know where the symlink points (without
> using an external program)?
My understanding is that it has been convention to use the "readlink"
program for a very long time, so there's never been
I've discovered a gap in POSIX compliance in lib/sh/strftime.c on the devel
branch. POSIX mandates that the timeval struct be defined in ,
although as can be seen on Line 67 of the file in question, the file is only
included here if the tm struct -- which POSIX mandates be defined in
-- is def
