Re: Re: Re: Re: [PATCH 0/4] Add import builtin

2024-05-04 Thread Oğuz
On Sun, May 5, 2024 at 7:36 AM Matheus Afonso Martins Moreira wrote: > I certainly intend to use it as one should it be merged. If it's not you should try turning this into a loadable builtin. An `include' command that lets you selectively import variables/functions from a larger collection and n

Re: Re: Re: Re: [PATCH 0/4] Add import builtin

2024-05-04 Thread Matheus Afonso Martins Moreira
> If your purpose is just to solve a small inconvenience of the `source' > builtin mixing the namespaces of local scripts, "libraries", and > executables, I think the suggested `source -i' or `source -l' would be > fine. I think no additional reasoning is needed. That is my purpose! I think I wen

Re: 5.3-alpha: the `jobs' builtin prints foreground dead jobs with function substitutions

2024-05-04 Thread Koichi Murase
2024年5月3日(金) 23:36 Chet Ramey : > > To the email [2]. In particular, to the question in the second paragraph > > [2]. > > OK. No, it doesn't make sense to do that. > > The better option is to change the notification strategy so that the jobs > list doesn't contain terminated unnotified foreground

Re: Re: Re: [PATCH 0/4] Add import builtin

2024-05-04 Thread Koichi Murase
If your purpose is just to solve a small inconvenience of the `source' builtin mixing the namespaces of local scripts, "libraries", and executables, I think the suggested `source -i' or `source -l' would be fine. I think no additional reasoning is needed. In this case, the "#pragma once" feature wo

[sr #111058] Problem transmitting script arguments

2024-05-04 Thread anonymous
URL: Summary: Problem transmitting script arguments Group: The GNU Bourne-Again SHell Submitter: None Submitted: Sat 04 May 2024 10:08:41 AM UTC Category: None