Re: proposed BASH_SOURCE_PATH

[alex xmb sw ratchev]

s : BASH_SOURCE_REAL : BASH_SOURCE_ABSOLUTE

On Thu, Jul 25, 2024, 15:10 Chet Ramey <chet.ramey@case.edu> wrote:

> On 7/18/24 4:44 PM, konsolebox wrote:
> > On Thu, Jul 18, 2024 at 11:02 PM Chet Ramey <chet.ramey@case.edu> wrote:
> >>
> >> On 7/11/24 3:51 AM, konsolebox wrote:
> >>> On Thu, Jul 11, 2024 at 4:08 AM Chet Ramey <chet.ramey@case.edu>
> wrote:
> >>>> and the BASH_SOURCE
> >>>> absolute pathname discussion has been bananas, so that's not going in
> any
> >>>> time soon.
> >>>
> >>> Maybe just create BASH_SOURCE_REAL instead to avoid the gripes.
> >>
> >> I don't think so. It's not very useful to have two variables that are so
> >> similar -- it's needless overhead.
> >
> > So I guess it's really now just about BASH_SOURCE.  What's the final
> > decision on this?  I don't think waiting for more input would make a
> > difference.
>
> The best path forward is to enable the behavior with a new shell option,
> initially disabled.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>
>