It seems to me that Autoconf (configure) is making some bad choices if
it is just guessing that support exists like that, especially when it
has a guaranteed fallback. It's job is to setup the build for the
target host system. I was able to fix the build by using
--without-bash-malloc.
Hello.
Well first i was thinking of a "%*" special so i can say
"kill %*", but get_job_spec() and usage does not look promising.
The task: close all jobs at once (and dreaming of
%ID1-%ID2,ID3-ID4, etc). Ie i often (really) am doing things that
require many instances of less(1), or git(1) log,
On Wed, Nov 08, 2023 at 11:52:19PM +0700, Robert Elz wrote:
> Date:Tue, 7 Nov 2023 23:04:10 +0100
> From:Mike Jonkmans
> Message-ID: <20231107220410.gc27...@jonkmans.nl>
>
> | It makes sense to partition the builtins in three categories with
> | a separate name
On Wed, Nov 08, 2023 at 10:38:19AM -0500, Chet Ramey wrote:
> On 11/7/23 5:04 PM, Mike Jonkmans wrote:
>
> It depends on your requirements. If you want something that is easy to
> explain to users, you want to reduce the distinction between `intrinsics'
> and `regular builtins' to something as
Date:Tue, 7 Nov 2023 23:04:10 +0100
From:Mike Jonkmans
Message-ID: <20231107220410.gc27...@jonkmans.nl>
| In particular, a user function with the name of a standard utility,
| will be called at this point.
Yes. That much is very clear.
| Chet mentioned
On 11/7/23 5:37 PM, Mike Jonkmans wrote:
On Tue, Nov 07, 2023 at 11:49:25AM -0500, Chet Ramey wrote:
On 11/7/23 8:54 AM, Mike Jonkmans wrote:
...
Look at https://www.austingroupbugs.net/view.php?id=854 for a discussion
of this issue.
Thanks for the link, I find that very hard to read
On 11/7/23 5:04 PM, Mike Jonkmans wrote:
| > 1d) Lists 20 fixed utility names (like alias, cd etc.) that are
| > to be invoked at his point. No PATH search yet.
| > These are the `regular builtins'.
In the next standard the ones listed are the intrinsic builtins,
and
