Re: [PATCH 0/4] Add import builtin

On Mon, May 6, 2024 at 7:51 PM Kerin Millar wrote: > > > I'll put it in a little more detail, though no less plainly. I find the > terminology of "libraries" and "modules" to be specious in the context of a > language that has no support for namespaces, awkward scoping rules, a > problematic

Possible Typo for "Set" Section of Bash Reference Manual

Hi! I believe the Bash Reference Manual is missing a key note for using "set -o". On the man page for "bash" (https://tiswww.case.edu/php/chet/bash/bash.html), the following line is present * If *-o* is supplied with no /option-name/, the values of the current options are printed. If

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

On 5/6/24 10:01 AM, Koichi Murase wrote: Since no one notifies about foreground jobs that aren't terminated by signals, we can omit them from the discussion -- they are removed from the jobs list as soon as they terminate. I think this is my issue of interpreting the standard, but isn't the

Re: [sr #111058] Problem transmitting script arguments

On 5/6/24 2:15 PM, anonymous wrote: Follow-up Comment #5, sr #111058 (group bash): (Author of comment #2) Indeed, you have a point about there being a dedicated Support category. One of its problems - which you couldn't have been aware of - is that it doesn't mesh well with the help-bash and

Re: macOS 14 objc `+initialize` forced crash due to fork after thread

On 5/6/24 11:17 AM, Tom wrote: It looks like it's the call to setlocale() that creates the auxiliary threads, and the call to gettext() that forces the artificial crash. Yep, that's my understanding. Thanks. I'll add a call to gettext() that will happen right after bash sets its default

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

Date:Mon, 6 May 2024 23:01:16 +0900 From:Koichi Murase Message-ID: | Hmm, maybe you mean that a shell is free to anytime remove the | terminated foreground jobs from the list regardless of whether it has | been reported or not, and "all jobs whose ...

Re: [sr #111058] Problem transmitting script arguments

On Mon, 6 May 2024, at 7:01 PM, Dale R. Worley wrote: > anonymous writes: >> URL: >> >> >> Summary: Problem transmitting script arguments > >> Date: Sat 04 May 2024 10:08:41 AM UTC By: Anonymous >> I have the following problem with

Re: [sr #111058] Problem transmitting script arguments

anonymous writes: > URL: > > > Summary: Problem transmitting script arguments > Date: Sat 04 May 2024 10:08:41 AM UTC By: Anonymous > I have the following problem with transmitting arguments to a bash script > onward to an inside

Re: [PATCH 0/4] Add import builtin

On Mon, 6 May 2024, at 6:11 PM, Matheus Afonso Martins Moreira wrote: >>> A native way to source libraries. Built into bash, available to all users. >> That's the source builtin. > > It looks for scripts in directories meant for executables. > It prefers files with the executable bit set. > It's a

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

>> A native way to source libraries. Built into bash, available to all users. > That's the source builtin. It looks for scripts in directories meant for executables. It prefers files with the executable bit set. It's a native way to load bash scripts for sure. But it's not a native way to load

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

2024年5月6日(月) 23:01 Koichi Murase : > > The whole issue here is that in some circumstances bash defers that > > notification too long, and doesn't do it before the user can run `jobs'. > > You don't need to change `jobs' so it doesn't print foreground jobs > > that were terminated by a signal, you

Re: macOS 14 objc `+initialize` forced crash due to fork after thread

> It looks like it's the call to setlocale() that creates the auxiliary > threads, and the call to gettext() that forces the artificial crash. Yep, that's my understanding. > So any call to gettext() in the parent process before any fork would be > sufficient to complete the initialization? It

Re: macOS 14 objc `+initialize` forced crash due to fork after thread

On 5/3/24 10:31 PM, Tom wrote: That report has a work-around invoking a syntax error which presumably calls out to `setlocale`/`gettext` pre-`fork`, caching the result somewhere (`bash` or `gettext`?) such that the offending call post-`fork` on an unknown command doesn't trigger this issue.

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

Thank you. 2024年5月6日(月) 22:16 Chet Ramey : > On 5/4/24 8:47 PM, Koichi Murase wrote: > > If we take the theory that « the notification of the signaled > > foreground jobs are required because it is not considered `reported' > > by `$?' », given that the shells don't notify the normally terminated

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

On 5/4/24 8:47 PM, Koichi Murase wrote: If we take the theory that « the notification of the signaled foreground jobs are required because it is not considered `reported' by `$?' », given that the shells don't notify the normally terminated foreground jobs, the jobs builtins are still required

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

2024年5月6日(月) 14:28 Matheus Afonso Martins Moreira : > > I fail to see how this could possibly save "thousands and thousands > > of lines of code". > > How many lines of code were needed to implement the module managers? > Probably a lot of lines. I guessed it was in the "thousands of lines" >

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

On 5/3/24 4:46 PM, Robert Elz wrote: What I see (in 5.2, and 5.3 alpha 1) is: jacaranda$ bash-5.3a1 -c '( kill -9 $BASHPID )' bash-5.3a1: line 1: 29765 Killed ( kill -9 $BASHPID ) I have no idea what you think that "9" is useful for, IMO it is a waste of space, and just

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

2024年5月5日(日) 13:36 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

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

> Your proposition could not be 'builtin', you want a new 'model' with > 'packages/module' Yes. However, that was because I did not really know bash module managers existed. I immediately adopted a conservative approach once I was informed of their existence. I do not intend to develop the

Re: Re: Re: [PATCH 0/9] Add library mode to source builtin

> Libraries are 'compiled collection of object module', can be static/dynamic, > dynamic imply a runtime load. By this definition, dynamic languages and scripting languages don't have libraries. They clearly do have libraries. Sometimes they're called modules but it's the same thing. > This

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

On Mon, May 6, 2024 at 7:28 AM Matheus Afonso Martins Moreira < math...@matheusmoreira.com> wrote: > Yet the feature has been described as "irritating"! > I really don't understand the cause for this > and it's making me feel really unwelcome. > I think it is not personnal, you proposed