Since the predominant use case for compgen is generating output that then
gets split back up into an array, it seems like it would be nice to have an
option that avoids the extra steps (and their associated pitfalls)
From e75306bd43d4ed233a7fedddb060a6bdd9305fdc Mon Sep 17 00:00:00 2001
From: Gris
Currently, the getconf build fails on platforms (e.g. Android) without
confstr(3)
From c1a616fd5ff18a202ad934bbb23ba4d58685 Mon Sep 17 00:00:00 2001
From: Grisha Levit
Date: Thu, 13 Apr 2023 04:32:04 -0400
Subject: [PATCH] support getconf builtin build without confstr
---
examples/loadables/
2023年4月13日(木) 17:31 Grisha Levit :
> Since the predominant use case for compgen is generating output that then
> gets split back up into an array, it seems like it would be nice to have an
> option that avoids the extra steps (and their associated pitfalls)
I have related but unsubmitted patches
2023年4月13日(木) 17:57 Koichi Murase :
> The first patch `r0034.compgen-update-desc.patch' update the
> description of existing options in manuals before adding the
> description of the new option. The patch `r0034.compgen-zflag.patch'
> adds the option -z.
Sorry, the second patch is broken. I failed
On 4/13/23 4:54 AM, Grisha Levit wrote:
Currently, the getconf build fails on platforms (e.g. Android) without
confstr(3)
Thanks for the report. I think `getconf PATH' should always work, and
return the same value that `command -p' will use, so I'm going to do this
another way.
Chet
--
``The l
with bash-5.0.3, !foo-b reports
b
bash: b: command not found
even when foo-bar is in history.
there is nothing in the history expansion sectio of the man page which
would eve suggest that - cannot be part of string.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
"Word" means something different in history expansion than it does in the
rest of the shell, because it happens before the normal lexical processing.
In effect, it means the same as an identifier in C.
A history expansion consists of a line selector (!cmdname) optionally
followed by colon and a wo
